Re: [PATCH v3 0/3] Documentation: recommend the use of b4

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 9, 2026, 13:30 UTC
Message-ID: <xmqqh5nbsuxu.fsf@gitster.g>
In-Reply-To: <87a4t32a4g.fsf@emacs.iotcl.com>

Toon Claes <toon@iotcl.com> writes:

> Anyhow, I don't think it's worth it to keep bike shedding about this. In
> all methods we recommend to Cc people, I think that's more important
> then

Good point to stress about whom to involve.

> caring about how messages are threaded (for example, I've noticed
> LKML doesn't thread at all, i.e. `b4.send-same-thread=no` which is the
> default).

As long as it does not hurt automation, I do not care too much, but that default is somewhat surprising to me. The setting actively discourages tools from finding previous iterations.

> Bottom line, for me this series is good to go in.

Yeah, sounds good to me.

$ 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.