From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: "Patrick Steinhardt" <ps@pks.im>,
git@vger.kernel.org, "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>
Subject: Re: [PATCH v3 0/3] Documentation: recommend the use of b4
Date: Tue, 09 Jun 2026 06:30:05 -0700 [thread overview]
Message-ID: <xmqqh5nbsuxu.fsf@gitster.g> (raw)
In-Reply-To: <87a4t32a4g.fsf@emacs.iotcl.com> (Toon Claes's message of "Tue, 09 Jun 2026 14:04:15 +0200")
Toon Claes <toon@iotcl.com> writes:
> 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
Good point to stress about whom to involve.
> 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).
As long as it does not hurt automation, I do not care too much, but
that default is somewhat surprising to me. The setting actively
discourages tools from finding previous iterations.
> Bottom line, for me this series is good to go in.
Yeah, sounds good to me.
prev parent reply other threads:[~2026-06-09 13:30 UTC|newest]
Thread overview: 44+ 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-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-09 12:04 ` [PATCH v3 0/3] Documentation: recommend the use of b4 Toon Claes
2026-06-09 13:30 ` Junio C Hamano [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=xmqqh5nbsuxu.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=ps@pks.im \
--cc=ramsay@ramsayjones.plus.com \
--cc=szeder.dev@gmail.com \
--cc=taahol@utu.fi \
--cc=toon@iotcl.com \
--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