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

From: Toon Claes <toon@iotcl.com>
Date: Jun 9, 2026, 12:04 UTC
Message-ID: <87a4t32a4g.fsf@emacs.iotcl.com>
In-Reply-To: <20260608-pks-b4-v3-0-f5e497d10c56@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 12 quoted lines

> Hi,
>
> this small patch series wires up b4 in Git and recommends the use
> thereof via "MyFirstContribution", as discussed in [1].
>
> Changes in v3:
>   - I wasn't really able to judge consensus one way or the other
>     regarding the deep vs shallow nesting of cover letters, so I still
>     have the change to shallow nesting of cover letters part of this
>     series. If we continue to be split on this one (or if we favor the
>     current status quo) I'm happy to drop the first patch and adapt the
>     last patch to use deep nesting of cover letters instead.

Personally I don't care too much. I'm used to the shallow threading, so I'm fine with that.

Now on the other hand, looking at a few examples I see GitGitGadget does deep nesting. Wouldn't it make sense to be consistent?

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

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

-- 
Cheers,
Toon