[Monotone-devel] Re: Proposal for human readable revision IDs

[Bruce Stephens]

Zbynek Winkler <address@hidden> writes:

[...]

> It's been a while since I was thinking about this but the solution
> that I would be probably happy with would be a generation number
> (within a branch). That would be a global identifier that would
> sometimes select a group of things but that could be handled by
> appending part of the hash.

I like that idea.  I don't think it quite works, because "branch"
doesn't necessarily mean what you want it to.  If branch could
uniquely identify an ancestor, and if all the other revisions in the
branch were connected to that, then it would work, I think.  

But I don't think monotone's like that.  You can take any old working
tree, and do "monotone commit --branch=net.venge.monotone", and then
that revision is on that branch, even though it may be in no way
related by ancestry with any other revision on that branch.  

Maybe that doesn't matter, though.  You could have
b:net.venge.monotone/g:3, and if there are multiple revisions which
could be so described, then so be it.  I could go for that.

[...]