From: ydirson@free.fr
To: git list <git@vger.kernel.org>
Cc: dirson@bertin.fr, poulot@bertin.fr, ydirson@free.fr
Subject: Strange reachability inconsistency (apparently, at least...)
Date: Thu, 19 Feb 2015 16:03:37 +0100 (CET) [thread overview]
Message-ID: <324985759.551780546.1424358217833.JavaMail.root@zimbra39-e7.priv.proxad.net> (raw)
In-Reply-To: <144640746.551672305.1424355582540.JavaMail.root@zimbra39-e7.priv.proxad.net>
I have a (fsck-clean) git tree in which for 2 commits A and B:
* "git merge-base --is-ancestor A B" returns 0
* "git log B..A" returns a non-empty set of commits
I get this behaviour with 2.3.0 as well as with 2.1.3 and 1.7.12.
Is that a real bug or am I just misinterpreting something ?
next parent reply other threads:[~2015-02-19 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <144640746.551672305.1424355582540.JavaMail.root@zimbra39-e7.priv.proxad.net>
2015-02-19 15:03 ` ydirson [this message]
2015-02-22 23:30 ` Strange reachability inconsistency (apparently, at least...) Junio C Hamano
2015-02-23 6:44 ` 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=324985759.551780546.1424358217833.JavaMail.root@zimbra39-e7.priv.proxad.net \
--to=ydirson@free.fr \
--cc=dirson@bertin.fr \
--cc=git@vger.kernel.org \
--cc=poulot@bertin.fr \
/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).