Re: git-rev-list in local commit order
- From
- Thomas Gleixner <tglx@linutronix.de>
- Date
- May 15, 2005, 21:13 UTC
- Message-ID
- <1116191636.11872.195.camel@tglx>
- In-Reply-To
- <1102.10.10.10.24.1116189916.squirrel@linux1>
On Sun, 2005-05-15 at 16:45 -0400, Sean wrote:
> You can continue the personal attacks or you can simply explain to the > list what you are trying to accomplish and why it is important and why any > other proposal besides yours isn't worthy.
I did never say, that my proposal is the world formula, but I have more than once explained, why time is the worst source of information.
You keep beating on time as a reliable source of information and tell me that most people are completely happy with it. You must have access to a quite good opinion survey.
Time of files or time in commit blobs is not a reliable information to keep track of - workflows - history Thats all I'm talking about and it is the concern of others too.
In "git" repositories the only reliable source of information is the parent child relationship. This information is only partially reliable due to the head forward scenario. I think we agreed on this, right ? You have no other reliable source of information due to the fact that committer names are not unique.
> I disagree that they're inherently error prone, > steps can be taken to make them as secure as you desire.
You continue to propose stuff which is not viable. Can you enforce - NTP syncronisation - the correct usage of rsync options - timestamp aware backups
No, you can't.
Why did the mail people resort to "In-Reply-To", "Message-ID" and "References" ? Because time turned out to be an inreliable source of information. Please read the related discussions before you argue that time based solutions are sufficient.
Time is illusion.
tglx