2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: <hidden>
Date: 2016-06-15 23:03:52
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 ?
From: Junio C Hamano <hidden>
Date: 2016-06-15 23:03:53
On Thu, Feb 19, 2015 at 7:03 AM, [off-list ref] wrote:
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 ?
Sounds strange. Is it possible to share the repository (or an anonymised copy of it)?