Re: [PATCH] [RFD] Add repoid identifier to commit
- From
- Thomas Gleixner <tglx@linutronix.de>
- Date
- May 12, 2005, 22:06 UTC
- Message-ID
- <1115935604.11872.97.camel@tglx>
- In-Reply-To
- <2477.10.10.10.24.1115933520.squirrel@linux1>
On Thu, 2005-05-12 at 17:32 -0400, Sean wrote:
Show 7 quoted lines
> > How do you enforce correct timestamps ? > > When an object is committed locally it is set to the local time. You can > only have this feature when you use private commit objects (shared blobs > are okay). It doesn't matter if the timestamps are correct in the global > sense, just that they're correct for the local server, because they'll > only ever be compared against each other.
That limits the usefulness to a local place, which makes no sense in a distributed development scenario.
> By the way, repoid doesn't work when all the branches are done in the same > repository. You'd need to use something like repoid-branch.
Right. That was my basic idea to collect the information either from an environment variable or deduce it from the current wroking directory, which is unlikely to be the same for different branches. hpa's arguments against this approach are quite good but I think somethink like a per branch repository id is not too hard to implement.
tglx