Re: [PATCH 1/2] b4: introduce configuration for the Git project
- From
SZEDER Gábor <szeder.dev@gmail.com>
- Date
- Jun 3, 2026, 11:07 UTC
- Message-ID
- <aiAK9eLvew+mgWt+@szeder.dev>
- In-Reply-To
- <ah_PyDwO1Sffr5yq@pks.im>
On Wed, Jun 03, 2026 at 08:55:04AM +0200, Patrick Steinhardt wrote:
Show 15 quoted lines
> On Wed, Jun 03, 2026 at 10:12:22AM +0800, Weijie Yuan wrote: > > On Tue, Jun 02, 2026 at 08:09:55PM +0300, Tuomas Ahola wrote: > > > Huh? Doesn't MyFirstContribution speak *against* shallow threading? > > > > > > [...] make sure to replace it with the correct Message-ID for your > > > **previous cover letter** - that is, if you're sending v2, use the Message-ID > > > from v1; if you're sending v3, use the Message-ID from v2. > > > > I don't get it. Doesn't shallow threading means every following patches > > are replying to the cover letter? Replying to the previous one is > > --chain-reply-to, if I'm not mistaken. > > Shallow threading basically means that all patches are sent as a > response to the current cover letter, and the current cover letter is > always attached to the cover letter of the _first_ version.
No, in Git shallow threading means that all patches are sent as a respose to the current cover letter, period. It has nothing to do with whether the current cover letter is sent as a reply to the cover letter of the first or the previous version.
> So this quote is definitely at odds with the configuration I have > proposed. It's actually quite surprising to me that we recommend deep > threading -- I personally find it extremely hard to navigate as the > nesting eventually gets way too deep.
Deep threading means that every mail is a reply to the previous one. Again, it has nothing to do with the relation of the current cover letter and the previous cover letters.
Therefore, we do not recommend deep threading.
> You know -- I'll include a patch that changes the wording there to also > use shallow nesting, mostly to kick off a discussion and arrive at a > decision there.