From: Jeff King <peff@peff.net>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Kevin Bracey <kevin@bracey.fi>,
Git mailing list <git@vger.kernel.org>
Subject: Re: Weird revision walk behaviour
Date: Wed, 23 May 2018 13:35:23 -0400 [thread overview]
Message-ID: <20180523173523.GB10299@sigill.intra.peff.net> (raw)
In-Reply-To: <20180523173246.GA10299@sigill.intra.peff.net>
On Wed, May 23, 2018 at 01:32:46PM -0400, Jeff King wrote:
> On Wed, May 23, 2018 at 07:10:58PM +0200, SZEDER Gábor wrote:
>
> > $ git log --oneline master..ba95710a3b -- ci/
> > ea44c0a594 Merge branch 'bw/protocol-v2' into jt/partial-clone-proto-v2
> >
> > But as far as I can tell, there are no changes in the 'ci/' directory
> > on any of the merge's parents:
> >
> > $ git log --oneline master..ea44c0a594^1 -- ci/
> > # Nothing.
> > $ git log --oneline master..ea44c0a594^2 -- ci/
> > # Nothing!
>
> Hmm. That commit does touch "ci/" with respect to one of its parents.
> It should get simplified away because it completely matches the other
> parent, so it does sound like a bug.
>
> > This is not specific to the 'ci/' directory, it seems that any
> > untouched directory does the trick:
> >
> > $ git log --oneline master..ea44c0a594 -- contrib/coccinelle/ t/lib-httpd/
> > ea44c0a594 Merge branch 'bw/protocol-v2' into jt/partial-clone-proto-v2
>
> Both of those directories also differ between one parent. If you try it
> with "contrib/remote-helpers", which does not, then the commit does not
> appear.
>
> So it does seem like a bug where we should be simplifying away the merge
> but are not (or I'm missing the corner case, too ;) ).
>
> > I get the same behavior with Git built from current master and from
> > past releases as well (tried it as far back as v2.0.0).
>
> I keep some older builds around, and it does not reproduce with v1.6.6.3
> (that's my usual goto for "old"). Bisecting turns up d0af663e42
> (revision.c: Make --full-history consider more merges, 2013-05-16). It
> looks like an unintended change (the commit message claims that the
> non-full-history case shouldn't be affected).
There's more discussion in the thread at:
https://public-inbox.org/git/1366658602-12254-1-git-send-email-kevin@bracey.fi/
I haven't absorbed it all yet, but I'm adding Junio to the cc.
-Peff
next prev parent reply other threads:[~2018-05-23 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 17:10 Weird revision walk behaviour SZEDER Gábor
2018-05-23 17:32 ` Jeff King
2018-05-23 17:35 ` Jeff King [this message]
2018-05-24 18:54 ` Kevin Bracey
2018-05-24 20:26 ` Kevin Bracey
2018-05-27 17:37 ` Kevin Bracey
2018-05-28 22:06 ` SZEDER Gábor
2018-05-29 6:11 ` Kevin Bracey
2018-05-29 21:04 ` Jeff King
2018-05-30 8:20 ` Kevin Bracey
2018-05-31 5:43 ` Jeff King
2018-05-31 14:54 ` Kevin Bracey
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180523173523.GB10299@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kevin@bracey.fi \
--cc=szeder.dev@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).