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

Re: [PATCH] doc: add caveat about turning off commit-graph

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
May 7, 2026, 14:30 UTC
Message-ID
<3f0e03e4-f1ca-4010-aacf-72b3ce0aebd1@app.fastmail.com>
In-Reply-To
<5f9f4998-4538-4bc1-a245-4248e18c4e86@gmail.com>
On Wed, May 6, 2026, at 15:59, Derrick Stolee wrote:
Show 21 quoted lines
>>[snip]
>>
>> But this isn’t mentioned in the user-facing doc. Let’s mention it on
>> git-replace(1) and git-commit-graph(1).
>
> I like your initiative to present this incompatibility in the
> user-facing docs.
>
>> +CAVEATS
>> +-------
>> +
>> +The existence of replace objects or commit grafts turns off reading or
>> +writing to the commit-graph. See linkgit:git-replace[1].
>> +
> This does seem a little weak. It doesn't really say how this will
> impact the user. Perhaps we could add something about how performance
> will likely degrade in this mode?
>
>   The existence of replace objects or commit grafts turns off reading or
>   writing to the commit-graph, which can cause performance issues. See
>   linkgit:git-replace[1].

Thanks, that’s good. But I think this addition makes sense only on git-replace(1). In this (example) git-commit-graph(1) case the whole doc already explains what the commit-graph is about.

Previous: Derrick StoleeNext: Derrick Stolee
Message 3 of 12 in “doc: add caveat about turning off commit-graph”
  1. doc: add caveat about turning off commit-graphkristofferhaugsbakk@fastmail.com, May 5, 2026
  2. Derrick StoleeMay 6, 2026
  3. Kristoffer HaugsbakkMay 7, 2026
  4. Derrick StoleeMay 7, 2026
  5. doc: add caveat about turning off commit-graphkristofferhaugsbakk@fastmail.com, May 7, 2026
  6. Derrick StoleeMay 7, 2026
  7. doc: add caveat about turning off commit-graphkristofferhaugsbakk@fastmail.com, May 7, 2026
  8. Derrick StoleeMay 7, 2026
  9. Kristoffer HaugsbakkMay 7, 2026
  10. Junio C HamanoMay 11, 2026
  11. Oswald BuddenhagenMay 11, 2026
  12. Kristoffer HaugsbakkMay 20, 2026

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.