-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robin H. Johnson schrieb: > On Wed, Aug 27, 2008 at 12:37:09AM +0200, Ren?? 'Necoro' Neumann wrote: >> - --or: to have the unique rev-id instead of the branch-local rev-number-- >> bzr log -l1 --show-ids $FILE | grep "revision-id" | cut -f2 -d' ' > IIRC, the revision-id is just like the Git $Id$, it's a hex string, not > an incremented counter like the revision number in CVS. >
True ... it usually looks like [EMAIL PROTECTED] Though, if one enforces certain policies using the "main branch" located on the server like disallowing pushing and only allowing merges, one can safely use the branch-revno (which is incremental). Only oddity are revnos of merged branches (e.g. "193.1.10") Another approach would be to use the unix-timestamp of the last change. Though it is not a unique identifier per se, it should be sufficient here. It should be queriable in all VCS. Though it might be, that it is not possible using standard CLI and requires a plugin in some way (but I bet, an easy one ;)) - - Necoro -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAki0j3UACgkQ4UOg/zhYFuDZ+QCdGm7Sjew2+27KCUB06lWf8aLr XBsAoIbJSke4xHyPiucYEmkuNVd9GPJ3 =jTaO -----END PGP SIGNATURE-----
