From: David Woodhouse <dwmw2@infradead•org>
To: Linus Torvalds <torvalds@osdl•org>
Cc: Petr Baudis <pasky@ucw•cz>, "H. Peter Anvin" <hpa@zytor•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: kernel.org now has gitweb installed
Date: Thu, 28 Apr 2005 22:47:46 +0100 [thread overview]
Message-ID: <1114724866.2734.27.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0504281432490.18901@ppc970.osdl.org>
On Thu, 2005-04-28 at 14:40 -0700, Linus Torvalds wrote:
> Wrong. The date _does_ have meaning. It shows which of the parents was
> more recent, which indirectly is a hint about which side had more activity
> going on.
>
> In other words, it _is_ meanginful. Maybe it's a _statistical_ meaning
> ("that side is probably the active one, because it has the last commit"),
> but it's a meaning.
It's not entirely clear what 'active' is supposed to be useful for in
this instance. You could just as well count the commits between the
merge and the common ancestor, if you want to see which side was most
_active_ -- but that isn't helpful for deciding the order in which
'cg-log' should show commits.
What you really want there is 'local' vs. 'remote', because people want
to see the order in which changesets arrived in the _local_ repository
-- if the last thing you did was pull from me, people want all my
changesets to be at the top; regardless of who last committed to their
tree before the merge -- i.e. regardless of whether I did a last-minute
commit before you pulled, or whether you'd done another commit to your
tree immediately before pulling.
As you rightly point out, the local/remote information isn't really
available in an easy form -- certainly not from the ordering of the
parents in a merge commit. But let's not fool ourselves that we can
piece it together from the date either.
OK, the date _is_ meaningful in a way, but only in the same way that the
author's name and IRC address information is meaningful. Of course we
didn't include it for _nothing_, but it's outside the scope of git
itself; it isn't part of the useful information which git should care
about.
--
dwmw2
next prev parent reply other threads:[~2005-04-28 21:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 1:38 kernel.org now has gitweb installed H. Peter Anvin
2005-04-28 4:17 ` Daniel Jacobowitz
2005-04-28 7:35 ` David Woodhouse
2005-04-28 8:10 ` Petr Baudis
2005-04-28 8:29 ` David Woodhouse
2005-04-28 9:23 ` David Woodhouse
2005-04-28 18:55 ` Linus Torvalds
2005-04-28 21:20 ` David Woodhouse
2005-04-28 21:40 ` Linus Torvalds
2005-04-28 21:47 ` David Woodhouse [this message]
2005-04-28 21:50 ` H. Peter Anvin
2005-04-28 21:52 ` H. Peter Anvin
2005-04-28 22:12 ` Linus Torvalds
2005-04-28 22:12 ` David Woodhouse
2005-04-29 2:46 ` Jan Harkes
2005-04-28 21:21 ` Junio C Hamano
2005-04-28 21:23 ` David Woodhouse
2005-04-28 21:44 ` Junio C Hamano
2005-04-28 22:04 ` Linus Torvalds
2005-04-28 22:59 ` Gerhard Schrenk
2005-04-28 21:38 ` David Woodhouse
2005-04-28 21:49 ` Junio C Hamano
2005-04-28 21:44 ` Linus Torvalds
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=1114724866.2734.27.camel@localhost.localdomain \
--to=dwmw2@infradead$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=hpa@zytor$(echo .)com \
--cc=pasky@ucw$(echo .)cz \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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