Re: [PATCH 1/2] b4: introduce configuration for the Git project
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 2, 2026, 13:32 UTC
- Message-ID
- <xmqqldcxvziw.fsf@gitster.g>
- In-Reply-To
- <20260602-pks-b4-v1-1-a7ae5a49e9cf@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 23 quoted lines
> 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 <ps@pks.im> > --- > .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).