[RFC] CURRENT_TREE_REVISION ?

[Robert Collins]

I'm thinking of adding a new special revision marker, like null: is
today, which will be current:.

add_revision and get_revision will guard against this being
stored/retrieved.

It will be the revision id for the working tree.

This allows the following things without [much?|any?] special casing:

* bzr log can show the pending merges as being merged into the current
tree.
* bzr annotate can mark lines in the current tree vs lines that come
from a pending merge.

Possibly there are other applications for it.

I'm thinking of an api like 'tree.get_revision()' to get the revision
object that owns a tree. For EmptyTree this is a Revision object
representing 'null:', for WorkingTree this is a Revision object
representing 'current:' with parents matching the parents list of the
tree - i.e. null: for a newly inited tree.

Thoughts ?

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/20060616/fd93fb12/attachment.pgp