[MERGE] Fixes for 'bzr revision-info'

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bentley wrote:
> John Arbash Meinel wrote:
>>> I had a need to use 'bzr revision-info' and found that it was limited to
>>> only working in the current working tree. So the attached patch updates
>>> it to support '--directory' to supply any url, and not require a working
>>> tree.
> 
> I think we should follow the format of log and cat unless there's a good
> reason to deviate.  revision-info currently takes a revision id as an
> argument, but that's highly unusual.
> 
> Aaron

I agree, but it is the way it has been for a long time. And I didn't
feel like doing a deprecation song and dance.

I'm not even sure how you would deprecate something that drastic. I
guess you could deprecate passing a revision-id, and then after a while
you could bring in passing in a url.

Unless we feel that because the command is "hidden" it would be okay to
switch it to taking a location.

I don't know how people have used 'bzr revision-info', my personal uses
are fairly limited.

bzr log -r --short --show-ids shows pretty much the same information
(for what I'm trying to do). And if we fixed 'log -r' so it would work
on non mainline revisions then it would do what I need.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFuOYZJdeBCYSNAAMRAhyoAKCQJa3ddDSwhJ9RBcOOkyDk6ur1/wCfWMOW
sTbiA5MnPm59bUt2TCshBfA=
=2sf1
-----END PGP SIGNATURE-----