a way to reference pending revisions (pending:)

[John A Meinel]

At the moment, after a "bzr merge" you get a list of pending merges, but you don't have a good way to reference them, in case you want to "bzr log" or "bzr diff" what they introduce.

One suggestion is to possibly number the pending merges in some way, so that you could do:

bzr diff -r pending:1..pending:2

If 'bzr status' showed them with a number preceding each, it would be fairly easy to follow.

jkakar on IRC suggested just a simple in-order numbering, so the 1st entry gets the value 1, etc.

In theory, this may not be too hard to do. The biggest problem is that our revisionspec code is all built around looking them up in the Branch or possibly Repository. But this would require looking in the WorkingTree (and then building the newly merged info graph, etc.)

Another slight possibility is my "short revspec" code, which let you supply just portions of a revision id, and it would look up the details. And then you could "bzr status --verbose" which would expose the revision ids to look up.

[Aaron Bentley (abentley)]

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

John A Meinel wrote:
> In theory, this may not be too hard to do. The biggest problem is that
> our revisionspec code is all built around looking them up in the Branch
> or possibly Repository.

We'll need to fix this for the 'current:' revision (which refers to the
working tree) also.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGw0Ee0F+nu1YWqI0RAjFOAJ0QIzg5+DMJUGPxeZo9+4hV4eH15wCfbix+
3f/CQsak7d2zWDEh15kIheM=
=UwP3
-----END PGP SIGNATURE-----