On Mon, 2006-10-23 at 20:31 +0200, Jakub Narebski wrote: > Jelmer Vernooij wrote: > >> By the way, I wonder if accidentally identical revisions > >> (see example for accidental clean merge on revctrl.org) > >> would get the same revision id in bzr. In git they would. > > > They won't. The revision id is made up of the committers email address, > > a timestamp and a bunch of random data. It wouldn't be hard to switch > > using checksums as revids instead, but I don't think there are any plans > > in that direction. > The place for timestamp and commiter info is in the revision metadata > (in commit object in git). Not in revision id. Unless you think that > "accidentally the same" doesn't happen... The revision id isn't parsed by bzr. It's just a unique identifier that is generated at commit-time and is currently created by concatenating those three fields. It can be anything you like. The bzr-svn plugin for example creates revision ids in the form svn:REVNUM@REPOS_UUID-BRANCHPATH and bzr-git uses git:GITREVID. Nothing will break if bzr would start using a different format. Cheers, Jelmer -- Jelmer Vernooij <jelmer@xxxxxxxxx> - http://samba.org/~jelmer/
Attachment:
signature.asc
Description: This is a digitally signed message part