From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] b4: introduce configuration for the Git project
Date: Tue, 02 Jun 2026 22:32:23 +0900 [thread overview]
Message-ID: <xmqqldcxvziw.fsf@gitster.g> (raw)
In-Reply-To: <20260602-pks-b4-v1-1-a7ae5a49e9cf@pks.im> (Patrick Steinhardt's message of "Tue, 02 Jun 2026 13:59:09 +0200")
Patrick Steinhardt <ps@pks.im> 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 <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).
next prev parent reply other threads:[~2026-06-02 13:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 11:59 [PATCH 0/2] Documentation: recommend the use of b4 Patrick Steinhardt
2026-06-02 11:59 ` [PATCH 1/2] b4: introduce configuration for the Git project Patrick Steinhardt
2026-06-02 13:32 ` Junio C Hamano [this message]
2026-06-02 14:56 ` Patrick Steinhardt
2026-06-02 16:23 ` Ramsay Jones
2026-06-03 2:59 ` Junio C Hamano
2026-06-03 6:52 ` Patrick Steinhardt
2026-06-02 17:09 ` Tuomas Ahola
2026-06-03 2:12 ` Weijie Yuan
2026-06-03 6:55 ` Patrick Steinhardt
2026-06-03 7:50 ` Weijie Yuan
2026-06-03 9:51 ` Weijie Yuan
2026-06-03 11:07 ` SZEDER Gábor
2026-06-03 12:23 ` Weijie Yuan
2026-06-02 11:59 ` [PATCH 2/2] Documentation/MyFirstContribution: recommend the use of b4 Patrick Steinhardt
2026-06-02 16:09 ` Weijie Yuan
2026-06-03 6:54 ` Patrick Steinhardt
2026-06-03 7:53 ` Weijie Yuan
2026-06-03 8:00 ` Weijie Yuan
2026-06-03 6:58 ` [PATCH v2 0/3] Documentation: " Patrick Steinhardt
2026-06-03 6:58 ` [PATCH v2 1/3] Documentation/MyFirstContribution: recommend shallow threading Patrick Steinhardt
2026-06-03 10:01 ` Tuomas Ahola
2026-06-03 10:29 ` Weijie Yuan
2026-06-03 6:59 ` [PATCH v2 2/3] Documentation/MyFirstContribution: recommend the use of b4 Patrick Steinhardt
2026-06-03 6:59 ` [PATCH v2 3/3] b4: introduce configuration for the Git project Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqldcxvziw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox