From: Petr Baudis <pasky@ucw.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Stop git-rev-list at sha1 match
Date: Thu, 12 May 2005 01:44:55 +0200 [thread overview]
Message-ID: <20050511234455.GL22686@pasky.ji.cz> (raw)
In-Reply-To: <1115852914.22180.170.camel@tglx>
Dear diary, on Thu, May 12, 2005 at 01:08:34AM CEST, I got a letter
where Thomas Gleixner <tglx@linutronix.de> told me that...
> On Thu, 2005-05-12 at 00:50 +0200, Petr Baudis wrote:
> > > Rn
> > > ---- Stop = Rn-1
> > > Rn-1
> > > ---- Stop = Rn-2
> >
> > Mn
> > Mn-1
> >
> > > Rn-2
> > > ---- Stop = Rn-3
> > >
> > > The diff between Rn and Rn-1 contains always the changes merged from M
> >
> > Yes, but you get the merge commits again since rev-list follows all the
> > parents.
>
> That's plain wrong. The Mn(1) change hit repository r between revision
> Rn and Rn-1 and nowhere else.
>
> Date is irrelevant. The only relevant thing is the parent child(s)
> relationship.
What I described is just how rev-list works (now), nothing more. This is
what you get when you use rev-list.
Please see the thread of
5730 Apr 27 H. Peter Anvin ( 0.2K) kernel.org now has gitweb installed
for extensive discussion on how (it is impossible or very hard) to do
better.
So how would you order the list of commits?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-11 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 19:24 [PATCH] Stop git-rev-list at sha1 match Thomas Gleixner
2005-05-11 20:03 ` Junio C Hamano
2005-05-11 20:30 ` Thomas Gleixner
2005-05-11 21:54 ` Junio C Hamano
2005-05-11 22:17 ` Petr Baudis
2005-05-11 22:49 ` Thomas Gleixner
2005-05-11 22:50 ` Petr Baudis
2005-05-11 23:08 ` Thomas Gleixner
2005-05-11 23:44 ` Petr Baudis [this message]
2005-05-12 0:31 ` Thomas Gleixner
2005-05-13 5:26 ` Petr Baudis
2005-05-12 1:54 ` Junio C Hamano
2005-05-12 2:11 ` Junio C Hamano
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=20050511234455.GL22686@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.