From: Ramsay Jones Date: Tue, 02 Jun 2026 16:23:16 GMT Subject: Re: [PATCH 1/2] b4: introduce configuration for the Git project Message-ID: <8dbdb553-9633-46bb-8a51-040d06d0d10e@ramsayjones.plus.com> In-Reply-To: On 02/06/2026 2:32 pm, Junio C Hamano wrote: > Patrick Steinhardt writes: > >> We're about to extend our documentation to recommend b4 for sending >> patch series ot the mailing list. Prepare for this by introducing a b4 >> configuration so that the tool knows to honor our preferences. For now, >> this configuration does two things: >> >> - It configures "send-same-thread = shallow", which tells b4 to always >> send subsequent versions of the same patch series as a reply to the >> cover letter of the first version. >> >> - It configures "prep-cover-template", which tells b4 to use a custom >> template for the cover letter. The most important change compared to >> the default template is that our custom template also includes a >> range-diff. >> >> There's potentially more things that we may want to configure going >> forward, like for example auto-configuration of folks to Cc on certain >> patches. But these two tweaks feel like a good place to start. >> >> Signed-off-by: Patrick Steinhardt >> --- >> .b4-config | 3 +++ >> .b4-cover-template | 11 +++++++++++ >> 2 files changed, 14 insertions(+) > > Shipping a sample like ".b4-config.sample" that users who opt-in can > copy-and-edit into the final name ".b4-config" is OK, but I'd rather > not to ship the configuration files that the users would want to edit > (hence making the tree dirty). > Hmm, for those of us not in the know, perhaps mention the b4 documentation at 'b4.docs.kernel.org' (which includes how to install b4 ... ;) ). ATB, Ramsay Jones