git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Petr Baudis <pasky@ucw.cz>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: kernel.org now has gitweb installed
Date: Thu, 28 Apr 2005 14:52:48 -0700	[thread overview]
Message-ID: <42715B30.6010705@zytor.com> (raw)
In-Reply-To: <1114723214.2734.9.camel@localhost.localdomain>

David Woodhouse wrote:
> 
> Hmm, that's true; albeit unfortunate. 
> 
> Still, using the date isn't any better. It'll give results which are
> about as random as just sorting by the sha1 of each parent.
> 
> Yes, the ordering of the parents in a merge is probably meaningless in
> the general case, but so is the date.
> 
> The best we could probably do, from a theoretical standpoint, is to look
> at the paths via each parent to a common ancestor, and look at how many
> of the commits on each path were done by the same committer. Even that
> isn't ideal, and it's probably fairly expensive -- but it's pointless to
> pretend we can infer anything from _either_ the dates or the ordering of
> the parents in a merge.
> 

I thought about this for a few seconds (I really should do that more 
often...) and realized what it is you want: you want a primary search 
criterion which is "when did event X become visible to me", where "me" 
in this case is the web tool.  That is not repository information, but 
it is perfectly possible for the webtool to be aware of what it has 
previously seen and when.

And yes, this ordering is clearly different for each observer.

	-hpa

  parent reply	other threads:[~2005-04-28 21:47 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
2005-04-28 21:50             ` H. Peter Anvin
2005-04-28 21:52             ` H. Peter Anvin [this message]
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=42715B30.6010705@zytor.com \
    --to=hpa@zytor.com \
    --cc=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --cc=torvalds@osdl.org \
    /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).