Re: [PATCH] [RFD] Add repoid identifier to commit
- From
Sean <seanlkml@sympatico.ca>
- Date
- May 12, 2005, 21:32 UTC
- Message-ID
- <2477.10.10.10.24.1115933520.squirrel@linux1>
- In-Reply-To
- <1115932872.11872.86.camel@tglx>
On Thu, May 12, 2005 5:21 pm, Thomas Gleixner said:
>> And the time is recorded on the commit blob too. > > 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.
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.
One area where your repoid is superior that i missed in my previous email is that you can actually recover a corrupt blob from an unrelated repository that happens to contain it, and you've lost no information. Which is what Linus was expounding as one of the benefits of the git design.
Sean