[MERGE] Add an optional location parameter to the 'revision-history' command.

John Arbash Meinel john at arbash-meinel.com
Tue May 30 16:40:22 BST 2006


Michael Ellerman wrote:
> Hi guys,
> 
> This came in handy, so I coded it up properly.
> 
> Pullable from:
> http://michael.ellerman.id.au/bzr/branches/mpe/
> 
> I was going to do the same for 'ancestry', but there's a TODO in there
> about using tree.last_revision() instead of branch.last_revision() which
> got me confused. How would the working tree ancestry differ from the
> branches?
> 
> cheers

If you have a checkout (specifically lightweight checkout), it is
possible for the working tree to be out of date with respect to the
branch. (It is also possible if you push changes over sftp, since we
don't update the working tree).

If you want, you could probably leave this as a TODO, though I would
probably say "use the working tree if you can, else fall back to the
plain branch."


+1 on the patch you submitted, though.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060530/e9aa11c3/attachment.pgp 


More information about the bazaar mailing list