Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
	"Weijie Yuan" <wy@wyuan.org>, "Tuomas Ahola" <taahol@utu.fi>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/2] b4: introduce configuration for the Git project
Date: Mon, 8 Jun 2026 08:48:49 +0200	[thread overview]
Message-ID: <aiZl0ce7lnRrL4bv@pks.im> (raw)
In-Reply-To: <xmqqmrxbp0s6.fsf@gitster.g>

On Thu, Jun 04, 2026 at 10:11:37AM +0900, Junio C Hamano wrote:
> Having said that, I've seen a cover letter of iteration N (for any
> value of N > 1) that respondes to the cover letter of the initial
> iteration.  While it seems not to break "br" and the lore archive
> does not seem unhappy about it, I am not sure if tooling used by
> other people are also happy with it.

Yeah, I always use that style myself. I mostly prefer it because the
nesting for long-running patch series with many versions is eventually
getting out of hand and hard to navigate, and I haven't seen any tooling
breaking as a result of that style.

If I'm the only one who thinks that style to be preferable I am happy to
adapt. I'm not really sure yet what the consensus is -- I'll send one
more version that includes the changes, but if we continue to be split
or in favor of the current status quo I'll drop those in the next
version.

Thanks!

Patrick

  reply	other threads:[~2026-06-08  6:48 UTC|newest]

Thread overview: 42+ 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 [this message]
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

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=aiZl0ce7lnRrL4bv@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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