<p><font size=2 color=navy face=Arial>
Bzr is "tree-oriented" in the sense that it performs, by default, at the tree level.<br><br>Here are some examples:<br>* If you're three directories deep in your checkout and you run "commit"...<br>** ...Subversion will commit changes from the current directory and below.<br>** ...Bazaar will commit changes for your entire checkout.<br>* If you run "add"...<br>** Subversion will recurse *if* a directory below is not version-controlled.<br>** Bazaar will recurse into subdirectories regardless of whether the immediate directories below are version-controlled.<br><br>While Subversion made the leap of supporting atomic commits, Bazaar reflects this vision of atomicity more thouroughly by encouraging tree-level operations. When you perform directory-level commits, you're often creating a state that in the repostory that doesn't represent any tested, integrated codebase. For example, you could rename a function from a file in one directory and begin using the new name in another. Committing from either directory in Subversion would result in an atomic, but broken, copy in the repository, despite the fact that your working copy tested fine when you ran "commit."<br></font></p>
<p><hr size=2 width="100%" align=center tabindex=-1>
<font face=Tahoma size=2>
<b>From</b>: bazaar-bounces@lists.canonical.com <bazaar-bounces@lists.canonical.com>
<br><b>To</b>: bazaar@lists.canonical.com <bazaar@lists.canonical.com>
<br><b>Sent</b>: Sat Nov 29 08:47:28 2008<br><b>Subject</b>: Re: bzr for documents
<br></font></p>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
Thanks Stephen for such a detailed answer.<br><div class="gmail_quote"><br>On Sat, Nov 29, 2008 at 9:16 AM, Stephen J. Turnbull <span dir="ltr"><<a href="mailto:stephen@xemacs.org">stephen@xemacs.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>Give the file's name as an argument to the command. If you only want<br>
to see logs of commits that touched wd/file.txt, "bzr log wd/file.txt"<br>
will do that.<br>
<div class="Ih2E3d"></div></blockquote><div>Is something similar possible for bzr-gtk? <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div>First, bzr is not directory-oriented. It's tree-oriented; it will<br>
recurse into subdirectories.</blockquote><div><br>I dont understand.<br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
As for emulating RCS, just put file names in all your commands like<br>
you did with RCS. (Syntax may vary in a few cases where the file name<br>
would for some reason mean something else to bzr, but mostly just<br>
append the file name as above.)<br>
</blockquote><div><br>Ok Thats (probably) what I want.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
HTH<br>
<br>
</blockquote></div>Yes Thanks<br>