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

Re: What's cooking in git.git (Jun 2026, #01)

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Jun 2, 2026, 11:53 UTC
Message-ID
<5203b303-e193-40cb-8b2d-3bc74cf77811@app.fastmail.com>
In-Reply-To
<xmqqy0gxw5i9.fsf@gitster.g>
On Tue, Jun 2, 2026, at 13:23, Junio C Hamano wrote:
Show 13 quoted lines
>[snip]
> * kh/doc-replay-config (2026-05-21) 4 commits
>  - doc: replay: move “default” to the right-hand-side
>  - doc: replay: use a nested definition list
>  - doc: replay: simplify replay.refAction description
>  - doc: link to config for git-replay(1)
>
>  Doc update for "git replay" to actually refer to its configuration
>  variables.
>
>  Will merge to 'next'.
>  cf. <xmqqpl2ced7d.fsf@gitster.g>
>  source: <CV_doc_replay_config.709@msgid.xyz>

Sorry, I meant to reply to your review but it fell out of the back of my mind. I will do that now.

I think making a second version will make sense.
>[snip]
Previous: Junio C Hamano
Message 2 of 2 in “What's cooking in git.git (Jun 2026, #01)”
  1. Junio C HamanoJun 2, 2026
  2. Kristoffer HaugsbakkJun 2, 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.