[RFC] "short" revision id spec.

[James Westby]

On (10/04/07 21:40), John Arbash Meinel wrote:
> http://bzr.arbash-meinel.com/plugins/short_revid_spec
> 
> I just wrote a plugin to implement a pattern matching on revision-id
> spec. Basically, it allows you to write a snippet of most revision ids,
> and have bzr do the hard work of matching to a real revision id.

I like this idea.

> 
> 2) I don't really like 'srevid:' and grabbing 'r:' seemed a little bit
> greedy. I'm okay with it in a plugin, because plugins let you do things
> like be greedy. Because it doesn't have to work for everyone everywhere.
> Any thoughts on what the prefix should be?

r: seems fine to me. Nothing less than about 20 chars is going to convey
what it means, so just make it short and easy to remember, and then when
people find out about it they will remember it.

> 3) r:x--y versus r:x-y or other forms. I chose -- because I prefer the
> look of it. The single dash looked like I was actually trying to match
> part of the revision id, rather than only trying to match the prefix and
> suffix.

I too prefer the double dash. Is x---y overkill? Would it help with
Arch?

Are there any printing characters invalid in a revision id?

On IRC John and I discussed having this also available without the
prefix, so that

  $ bzr log -r abcd

would match the revid in question. It should be pretty unambiguous when
a revno is given and when a revid is given. The r: prefix is still there
to get a revid if the entropy ends in digits.

Thanks,

James

-- 
  James Westby   --    GPG Key ID: B577FE13    --     http://jameswestby.net/
  seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256