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

Re: commit-graph: change in "best" merge-base when ambiguous

From
Jacob Keller <jacob.keller@gmail.com>
Date
May 21, 2018, 22:25 UTC
Message-ID
<CA+P7+xpC6bSy0wJhmgT=UMev2AdDz0LVG11Ok7Y5j0Fsr-s08Q@mail.gmail.com>
In-Reply-To
<20180521215443.GC16623@sigill.intra.peff.net>
On Mon, May 21, 2018 at 2:54 PM, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> Yes, I think this is clearly a case where all of the single merge-bases
> we could show are equally good. And I don't think we should promise to
> show a particular one, but I _do_ think it's friendly for us to have
> deterministic tie-breakers (we certainly don't now).
>
> -Peff

Right. I think we should probably have some mechanism that will allow us to always give the same answer, even if it's somewhat arbitrary.

Regards, Jake

Previous: Jeff KingNext: Michael Haggerty
Message 6 of 10 in “commit-graph: change in "best" merge-base when ambiguous”
  1. Derrick StoleeMay 21, 2018
  2. Elijah NewrenMay 21, 2018
  3. Jeff KingMay 21, 2018
  4. Stefan BellerMay 21, 2018
  5. Jeff KingMay 21, 2018
  6. Jacob KellerMay 21, 2018
  7. Michael HaggertyMay 22, 2018
  8. Derrick StoleeMay 22, 2018
  9. Jakub NarebskiMay 24, 2018
  10. Michael HaggertyMay 25, 2018

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.