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

[Robert Collins]

On Tue, 2006-05-30 at 10:40 -0500, John Arbash Meinel wrote:
> 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.

+1

Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060601/545b5a8b/attachment.pgp