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

Re: [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 8, 2023, 18:06 UTC
Message-ID
<xmqqlea436xo.fsf@gitster.g>
In-Reply-To
<e197cbd28135df5523ff5ba1688566edb831f037.1701927372.git.stanhu@gmail.com>
Stan Hu <stanhu@gmail.com> writes:
Show 10 quoted lines
> +[[configure-shallow-threads]]
> +=== Configuring shallow threads for `git format-patch`
> +
> +It is common practice on the Git mailing list to use "shallow" threads,
> +where every mail is a reply to the first mail of the series. You can
> +configure the default threading style of `git format-patch` via:
> +
> +-----
> +$ git config format.thread shallow
> +----

Hmph, I do not think I have such an option defined, yet I send out my series as "shallow" threads. I think the new description is somewhat misleading as-is. Isn't it applicable ONLY to those who let "format-patch" decide the message ID for patches? If the user lets "git send-email" assign the message IDs (and hence the thread structure), the configuration variable would not apply, no?

Previous: Stan Hu
Message 2 of 2 in “MyFirstContribution: configure shallow threads for git format-patch”
  1. 1/1 MyFirstContribution: configure shallow threads for git format-patchStan Hu, Dec 7, 2023
  2. Junio C HamanoDec 8, 2023

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.