git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Strange reachability inconsistency (apparently, at least...)

From
Yydirson@free.fr <ydirson@free.fr>
Date
Feb 19, 2015, 15:03 UTC
Message-ID
<324985759.551780546.1424358217833.JavaMail.root@zimbra39-e7.priv.proxad.net>
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: Junio C Hamano
Message 1 of 3 in “Strange reachability inconsistency (apparently, at least...)”
  1. ydirson@free.frFeb 19, 2015
  2. Junio C HamanoFeb 22, 2015
  3. Junio C HamanoFeb 23, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.