<div dir="ltr"><div>Ok, I've read a bit about the distributed concept.</div> <div> </div> <div>Anyway, I still have this need : </div> <div> </div> <div>I'm coding from multiple computer (ie same person behind muliple computer, same project, working on the same 'logical branch') : </div> <div></div> <ul> <li>My home computer</li> <li>My laptop</li> <li>My company computer</li></ul> <div>Also, contributor may want to join.</div> <div> </div> <div>I'd like to publish my commit on my linux server at home for the following reason : </div> <ul> <li>It's backed up (RAID 1 + backup export to a remote site)</li> <li>If my last change is on my laptop, in a cvs way of thinking, I would do a commit so that my changes are available to my other machine.</li> <li>have a place where official build are</li></ul> <div>Isn't it right to want to do that?</div> <div> </div> <div>Thomas</div> <div> </div> <div> </div> <div class="gmail_quote">On Mon, Oct 6, 2008 at 19:34, Paul LeoNerd Evans <span dir="ltr"><<a href="mailto:leonerd@leonerd.org.uk">leonerd@leonerd.org.uk</a>></span> wrote:<br></div> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div class="Ih2E3d">On Sat, 4 Oct 2008 16:26:57 +0200<br>"Thomas Manson" <<a href="mailto:dev.mansonthomas@gmail.com">dev.mansonthomas@gmail.com</a>> wrote:<br><br>> So the output will be the actual bazaar repository?<br> <br></div>Yes.<br><br>Coming from CVS, you're thinking about things in a bit the wrong way. CVS<br>has a "repository" which is the entity that lives on the server, and<br>various checkout directories, which live on the "clients". The repository<br> itself has a location (the CVSROOT), and each project stored there has a<br>name (the module name).<br><br>bzr doesn't do this. A bzr "branch" stores a project's revision history,<br>and a "checkout" is a place to work on the files stored there. There is<br> no distinction between the identity of a branch, and a location you can<br>access it from. The branch stored at e.g.<br><a href="http://bazaar.my.company/code/thing" target="_blank">http://bazaar.my.company/code/thing</a> is just that - a bare location.<br> <br>Any way to access that branch (HTTP, local file, SFTP, ...) counts as a<br>server. A "server" or "central repository" is a concept bzr itself<br>doesn't have; it comes as a consequence of your procedures to access it.<br> For example, you might have an SFTP server called <a href="http://repo.my.company.name/" target="_blank">repo.my.company.name</a><br>which you declare as the server. This is an entirely human-level concept<br>which bzr doesn't care about. The output here in your case, is a<br> directory tree containing branches. This tree is suitable for use as such<br>a server.<br><font color="#888888"><br>--<br>Paul "LeoNerd" Evans<br><br><a href="mailto:leonerd@leonerd.org.uk">leonerd@leonerd.org.uk</a><br> ICQ# 4135350       |  Registered Linux# 179460<br><a href="http://www.leonerd.org.uk/" target="_blank">http://www.leonerd.org.uk/</a><br></font></blockquote><br></div>