Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Toon Claes <toon@iotcl.com>
Cc: git@vger.kernel.org, "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>
Subject: Re: [PATCH v3 0/3] Documentation: recommend the use of b4
Date: Wed, 10 Jun 2026 08:42:29 +0200	[thread overview]
Message-ID: <aikHVTYVGw23E_Se@pks.im> (raw)
In-Reply-To: <87a4t32a4g.fsf@emacs.iotcl.com>

On Tue, Jun 09, 2026 at 02:04:15PM +0200, Toon Claes wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> Now on the other hand, looking at a few examples I see GitGitGadget does
> deep nesting. Wouldn't it make sense to be consistent?

I've chatted with Dscho about this, and he mentioned that Stolee has
already opened [1]. So yes, if we agree to change the recommendation we
should also adapt GGG.

Patrick

[1]: https://github.com/gitgitgadget/gitgitgadget/issues/2254

      parent reply	other threads:[~2026-06-10  6:42 UTC|newest]

Thread overview: 47+ 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-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-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 [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=aikHVTYVGw23E_Se@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --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