From: Thomas Gleixner <tglx@linutronix.de>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: git-rev-list in local commit order
Date: Sun, 15 May 2005 23:13:56 +0200 [thread overview]
Message-ID: <1116191636.11872.195.camel@tglx> (raw)
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
next prev parent reply other threads:[~2005-05-15 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 21:44 git-rev-list in local commit order Sean
2005-05-15 19:48 ` Thomas Gleixner
2005-05-15 19:57 ` Sean
2005-05-15 20:44 ` Thomas Gleixner
2005-05-15 20:45 ` Sean
2005-05-15 21:13 ` Thomas Gleixner [this message]
2005-05-15 21:21 ` Sean
2005-05-15 21:30 ` Thomas Gleixner
2005-05-15 21:43 ` Sean
2005-05-15 22:13 ` Thomas Gleixner
2005-05-16 21:25 ` Sean
2005-05-16 23:46 ` Linus Torvalds
2005-05-17 9:52 ` Thomas Gleixner
2005-05-17 15:43 ` Linus Torvalds
2005-05-17 17:05 ` Thomas Gleixner
2005-05-17 17:44 ` Linus Torvalds
2005-05-18 5:16 ` Jon Seymour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1116191636.11872.195.camel@tglx \
--to=tglx@linutronix.de \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).