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

Re: Split commit graphs and commit-graph read

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 11, 2019, 02:09 UTC
Message-ID
<xmqq1rufjh9n.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<87f16645-6af4-9703-1d0d-eb64728d2849@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
Show 7 quoted lines
> To fix this issue, I would probably go about it by removing the "read"
> subcommand and creating a "test-tool read-commit-graph" for the tests
> that need that output.
>
> If others on-list think that the better thing to do is to update the
> "read" subcommand to provide the same output, but iterate over each
> layer of an incremental commit-graph, then I can do that work instead.

I think moving it to test-tool is a good idea, whether the output presents a single result that consolidates all layers together, or allows to name just a single layer and shows its contents. I do not have a strong opinion between the two (both sounds usable debugging aid).

Thanks.
Previous: Derrick StoleeNext: Jeff King
Message 3 of 5 in “Split commit graphs and commit-graph read”
  1. Bryan TurnerNov 8, 2019
  2. Derrick StoleeNov 11, 2019
  3. Junio C HamanoNov 11, 2019
  4. Jeff KingNov 11, 2019
  5. Bryan TurnerNov 12, 2019

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.