From: H. Peter Anvin <hpa@zytor.com>
Date: Wed, 11 May 2005 23:14:21 GMT
Subject: Re: [PATCH] [RFD] Add repoid identifier to commit
Message-ID: <428291CD.7010701@zytor.com>
In-Reply-To: <1115847510.22180.108.camel@tglx>

Thomas Gleixner wrote:
> This is an initial attempt to enable history tracking for multiple
> repositories in a consistent state. At the moment this can only be done
> by heuristic guessing on the parent dates and the committer names. 
> This fails for example with Dave Millers net-2.6 and sparc-2.6 trees, as
> in both cases the committer name is the same. It fails also completely
> in cases where the system clock of the committer is wrong and the merge
> is a head forward. The old bk repository contains entries from 1999 and
> 2027, which will happen also with git over the time. 
> 
> To identify a repository commit-tree tries to read an environment
> variable "GIT_REPOSITORY_ID" and has a fallback to the current working
> directory. The environment variable keeps the door open for managed
> repository id's, but the current working directory is certainly a quite
> helpful information to solve the origin decision for history tracking.
> 
> Adding a line after the committer should not break any existing tools
> AFAICS.
> 

I would like to suggest a few limiters are set on the repoid.  In 
particular, I'd like to suggest that a repoid is a UUID, that a file is 
used to track it (.git/repoid), and that if it doesn't exist, a new one 
is created from /dev/urandom.

	-hpa