Git development
 help / color / mirror / Atom feed
From: Toon Claes <toon@iotcl.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Tuomas Ahola" <taahol@utu.fi>, "Weijie Yuan" <wy@wyuan.org>,
	"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
	"SZEDER Gábor" <szeder.dev@gmail.com>,
	"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
	"Karthik Nayak" <karthik.188@gmail.com>
Subject: Re: [PATCH v4 0/3] Documentation: recommend the use of b4
Date: Tue, 16 Jun 2026 08:40:14 +0200	[thread overview]
Message-ID: <87eci7yomp.fsf@emacs.iotcl.com> (raw)
In-Reply-To: <20260615-pks-b4-v4-0-22cfca8f19c5@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> Hi,
>
> this small patch series wires up b4 in Git and recommends the use
> thereof via "MyFirstContribution", as discussed in [1].
>
> Changes in v4:
>   - Improve a commit message.
>   - Link to v3: https://patch.msgid.link/20260608-pks-b4-v3-0-f5e497d10c56@pks.im
>
> 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.
>   - Hopefully fix some confusion by saying "shallow/deep threading of
>     cover letters".
>   - Fix some more instances where we recommend deep threading of cover
>     letters.
>   - Link to v2: https://patch.msgid.link/20260603-pks-b4-v2-0-a8aea0aa2c23@pks.im
>
> Changes in v2:
>   - Reorder commits so that the b4 docs are added first.
>   - Add a section that highlights how to configure b4, and that points
>     out that the per-project defaults can be overridden via Git
>     configuration.
>   - Add a patch to MyFirstContribution that recommends shallow
>     threading. I mostly intend this to be a discussion starter so that
>     the `.b4-config` file matches our preferred threading style.
>   - Fix a typo.
>   - Link to v1: https://patch.msgid.link/20260602-pks-b4-v1-0-a7ae5a49e9cf@pks.im
>
> Thanks!
>
> Patrick
>
> [1]: <xmqqik81xpqx.fsf@gitster.g>
>
> ---
> Patrick Steinhardt (3):
>       MyFirstContribution: recommend shallow threading of cover letters
>       MyFirstContribution: recommend the use of b4
>       b4: introduce configuration for the Git project
>
>  .b4-config                             |   6 ++
>  .b4-cover-template                     |  11 ++++
>  Documentation/MyFirstContribution.adoc | 100 ++++++++++++++++++++++++++++++---
>  Documentation/SubmittingPatches        |   6 +-
>  4 files changed, 114 insertions(+), 9 deletions(-)
>
> Range-diff versus v3:
>
> 1:  1aec56f76c = 1:  b6b488e6a8 MyFirstContribution: recommend shallow threading of cover letters
> 2:  f2036769bd = 2:  1a68b993d2 MyFirstContribution: recommend the use of b4
> 3:  fb522c7d90 ! 3:  5bc8fba96a b4: introduce configuration for the Git project
>     @@ Metadata
>       ## Commit message ##
>          b4: introduce configuration for the Git project
>      
>     -    We're about to extend our documentation to recommend b4 for sending
>     -    patch series to 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:
>     +    In the preceding commit we have extended our documentation to recommend
>     +    b4 for sending patch series to the mailing list. Introduce configuration
>     +    so that it knows to honor preferences of the Git project by default. 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

No further comments based on the range-diff.

-- 
Cheers,
Toon

      parent reply	other threads:[~2026-06-16  6:40 UTC|newest]

Thread overview: 54+ 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
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-03 13:30           ` Tuomas Ahola
2026-06-04  1:11           ` Junio C Hamano
2026-06-08  6:48             ` Patrick Steinhardt
2026-06-08  6:48           ` Patrick Steinhardt
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-08  6:48       ` Patrick Steinhardt
2026-06-03 10:29     ` Weijie Yuan
2026-06-08  6:48       ` Patrick Steinhardt
2026-06-08  8:31         ` Weijie Yuan
2026-06-03 20:09     ` Kristoffer Haugsbakk
2026-06-08  6:48       ` Patrick Steinhardt
2026-06-03  6:59   ` [PATCH v2 2/3] Documentation/MyFirstContribution: recommend the use of b4 Patrick Steinhardt
2026-06-04  5:25     ` Toon Claes
2026-06-08  6:48       ` Patrick Steinhardt
2026-06-03  6:59   ` [PATCH v2 3/3] b4: introduce configuration for the Git project Patrick Steinhardt
2026-06-03 13:58     ` Toon Claes
2026-06-08  6:48       ` Patrick Steinhardt
2026-06-08  6:49 ` [PATCH v3 0/3] Documentation: recommend the use of b4 Patrick Steinhardt
2026-06-08  6:49   ` [PATCH v3 1/3] MyFirstContribution: recommend shallow threading of cover letters Patrick Steinhardt
2026-06-10 11:08     ` Karthik Nayak
2026-06-15 12:58       ` Patrick Steinhardt
2026-06-08  6:49   ` [PATCH v3 2/3] MyFirstContribution: recommend the use of b4 Patrick Steinhardt
2026-06-08  6:49   ` [PATCH v3 3/3] b4: introduce configuration for the Git project Patrick Steinhardt
2026-06-10 11:13     ` Karthik Nayak
2026-06-15 12:58       ` Patrick Steinhardt
2026-06-09 12:04   ` [PATCH v3 0/3] Documentation: recommend the use of b4 Toon Claes
2026-06-09 13:30     ` Junio C Hamano
2026-06-10  6:42     ` Patrick Steinhardt
2026-06-15 12:59 ` [PATCH v4 " Patrick Steinhardt
2026-06-15 12:59   ` [PATCH v4 1/3] MyFirstContribution: recommend shallow threading of cover letters Patrick Steinhardt
2026-06-15 12:59   ` [PATCH v4 2/3] MyFirstContribution: recommend the use of b4 Patrick Steinhardt
2026-06-15 12:59   ` [PATCH v4 3/3] b4: introduce configuration for the Git project Patrick Steinhardt
2026-06-16  6:40   ` Toon Claes [this message]

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=87eci7yomp.fsf@emacs.iotcl.com \
    --to=toon@iotcl.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=karthik.188@gmail.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=ps@pks.im \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=szeder.dev@gmail.com \
    --cc=taahol@utu.fi \
    --cc=wy@wyuan.org \
    /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