Re: git-rev-list in local commit order

From: Sean <seanlkml@sympatico.ca>
Date: May 15, 2005, 21:43 UTC
Message-ID: <1392.10.10.10.24.1116193437.squirrel@linux1>
In-Reply-To: <1116192629.11872.201.camel@tglx>

On Sun, May 15, 2005 5:30 pm, Thomas Gleixner said:

Show 11 quoted lines

> On Sun, 2005-05-15 at 17:21 -0400, Sean wrote:
>> > Time is illusion.
>>
>> What you're missing is that time is only important in this case to
>> deduce
>> the relative age of each commit LOCALLY.   The intention of this
>> proposal
>> is not to allow time comparison of commits between repositories.
>
> I do not want to compare times. I want to figure out workflows and
> histories between different repositories.

Well I honestly don't know what you want. If I wanted to include a "fortune" line in every commit and couldn't explain what value it provided, i'd expect you or others to object.

My time based proposal solves the issue of :

Rn------\ Rn-1 Mn Rn-2 Mn-1 Rn-3 ---/ Initial

Showing up in two repositories sorted based on the order they were committed locally. This was an issue that you stated you were trying to solve. The test case works just as advertised. Remote times don't matter, all that matters is the time you merge the objects locally.

> Even LOCALLY is no guarantee for correct timestamps.

Sure, but then your repoid might have gone missing or be set incorrectly too. One nice thing if your time is wrong, you can simply reset the timestamp on the file. If your repo-id is wrong, you have to recast the commit object which will get a different SHA1 number and make things more difficult.

Sean