Re: [PATCH 2/2] Documentation/MyFirstContribution: recommend the use of b4

From: Weijie Yuan <wy@wyuan.org>
Date: Jun 3, 2026, 07:53 UTC
Message-ID: <ah_dh3uozNdYcL0_@wyuan.org>
In-Reply-To: <ah_PwOsbYfDCx0H2@pks.im>

On Wed, Jun 03, 2026 at 08:54:56AM +0200, Patrick Steinhardt wrote:

Show 15 quoted lines

> Ah, that's what you're hinting at. So you mean to say that folks should
> first understand the basics before basically automating all of the parts
> for them?
>
> I guess I can see where you're coming from, but I'm not sure I agree
> with this a 100%. My main goal is to make it easier for new community
> members to contribute to Git, and that means that we should automate all
> the hard parts as far as possible. This saves those new contributors
> from frustration, and it means that reviewers on the mailing list won't
> have to teach every single new contributor about how they should thread
> the mails, generate range-diffs and the like.
>
> So in the end, it saves both their and our time, but the learning
> opportunity is of course a bit diminished. I'd gladly accept that
> tradeoff though.

Yeah, after I expressed my opinion, I also felt a bit conflicted though. So I also agree with your intension.

Make an inappropriate metaphor: some usage of b4 and magit are "Porcelain" to Git. Whether how you are good at using those porcelains like magit or lazygit, in the end, you will eventually have to face git cli one day.

So the same for b4. If we list these three methods equally and simultaneously, the logic might be not that correct.

Your proposal:

           contribution workflow
                    |
    -------------------------------------
    |                 |                 |
    v                 v                 v
GitGitGadget   traditional email        b4
```

But I would frame it more like this:

           contribution workflow
                    |
        -------------------------
        |                       |
        v                       v
 GitGitGadget        traditional email workflow
                                      \
                                       \
                                       b4

For exmaple, If I am at this page the fisrt time:
    https://git-scm.com/docs/MyFirstContribution
And, I see these 3 ways, okay, I choose b4.

After installing b4 and reading some manuals, I would wonder: what's cover letter? what's Message-ID? So after a while, I would still have to learn those stuff and how b4 indeed optimize those complicated process.

So, to put it another way.. b4 is developed for high-level maintainers, who are apparently familiar with traditional ways. Therefore b4 saves their time. But for some beginers like me, I still have to know those concepts first.

But yeah, there are definitely some people would happily accept b4 and contribute easily. Thus, I agree this tradeoff.

-- Sent before reading v2, hope there's no conflict :-)