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>