From: "Sean" <seanlkml@sympatico.ca>
To: tglx@linutronix.de
Cc: git@vger.kernel.org
Subject: Re: git-rev-list in local commit order
Date: Sun, 15 May 2005 15:57:56 -0400 (EDT) [thread overview]
Message-ID: <4971.10.10.10.24.1116187076.squirrel@linux1> (raw)
In-Reply-To: <1116186533.11872.152.camel@tglx>
On Sun, May 15, 2005 3:48 pm, Thomas Gleixner said:
> On Sat, 2005-05-14 at 17:44 -0400, Sean wrote:
>> Attached is a preliminary hackish patch to sort git-rev-list in local
>> commit order.
>
> +unsigned long sha1_local_date(const unsigned char *sha1)
> +{
> + struct stat st;
> + if (find_sha1_file(sha1, &st))
> + return st.st_mtime;
> + return 0;
> +}
>
> Do you really want to base workflow and history information on file
> times ?
The local commit order just isn't all that important in many situations.
And for situations where it is important, this proposal seems completely
adequate. Mind you, the patch in question is complete crap.
> File times are local and completely error prone in distributed
> environments.
I disagree that they're inherently error prone, steps can be taken to make
them as secure as you desire. Also, many people just will not care about
this local-commit-time as they will simply be tracking a remote
repository. For applications like David Woodhouse's need to present the
newest commits first on a web page, this is _completely_ adequate. I've
yet to see an intended use for this information that isn't completely
handled by this proposal. Afterall, most people using git are getting by
just fine without such a facility today.
Regards,
Sean
next prev parent reply other threads:[~2005-05-15 19:57 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 [this message]
2005-05-15 20:44 ` Thomas Gleixner
2005-05-15 20:45 ` Sean
2005-05-15 21:13 ` Thomas Gleixner
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=4971.10.10.10.24.1116187076.squirrel@linux1 \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).