git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Patrick Steinhardt <ps@pks.im>
Date
Jun 3, 2026, 06:54 UTC
Message-ID
<ah_PwOsbYfDCx0H2@pks.im>
In-Reply-To
<ah8ALHMDVA2Gzz10@wyuan.org>
On Wed, Jun 03, 2026 at 12:09:16AM +0800, Weijie Yuan wrote:
Show 7 quoted lines
> > +Contributors are encouraged to use `b4`, which automates much of the
> > +bookkeeping that is otherwise done by hand.
> 
> So for statement like this and with my personal experience, I would say
> b4 is a more suitable option for senior contributors, as they already
> know, for example, what Message-ID and range-diffs are. But apparently,
> whose who use forges may not know.

I think it's perfectly suitable for newcomers, too. It automates so many of the concepts that a contributor has to learn way less about mailing list specific concepts, which reduces the learning curve.

Show 9 quoted lines
> Back to the patch, I think regarding b4 as a more advanced contribution
> way for those who had contributed via mailing lists for more than one
> time is a better expression or formulation. Here I mean "b4 prep", other
> usage like "b4 mbox" and "b4 am" are of course more basic, and be
> mentioned as tips when interacting with Git mailing list.
> 
> A bit too wordy, in conclusion: Suggest that new contributors master
> classic git operations first. When they are familiar with those process,
> b4 might be a good option.

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.

Thanks for your input!
Patrick
Previous: Weijie YuanNext: Weijie Yuan
Message 21 of 54 in “Documentation: recommend the use of b4”
  1. 0/2 Documentation: recommend the use of b4Patrick Steinhardt, Jun 2, 2026
  2. 1/2 b4: introduce configuration for the Git projectPatrick Steinhardt, Jun 2, 2026
  3. Junio C HamanoJun 2, 2026
  4. Patrick SteinhardtJun 2, 2026
  5. Ramsay JonesJun 2, 2026
  6. Junio C HamanoJun 3, 2026
  7. Patrick SteinhardtJun 3, 2026
  8. Tuomas AholaJun 2, 2026
  9. Weijie YuanJun 3, 2026
  10. Patrick SteinhardtJun 3, 2026
  11. Weijie YuanJun 3, 2026
  12. Weijie YuanJun 3, 2026
  13. SZEDER GáborJun 3, 2026
  14. Weijie YuanJun 3, 2026
  15. Tuomas AholaJun 3, 2026
  16. Junio C HamanoJun 4, 2026
  17. Patrick SteinhardtJun 8, 2026
  18. Patrick SteinhardtJun 8, 2026
  19. 2/2 Documentation/MyFirstContribution: recommend the use of b4Patrick Steinhardt, Jun 2, 2026
  20. Weijie YuanJun 2, 2026
  21. Patrick SteinhardtJun 3, 2026
  22. Weijie YuanJun 3, 2026
  23. Weijie YuanJun 3, 2026
  24. 0/3 Documentation: recommend the use of b4Patrick Steinhardt, Jun 3, 2026
  25. 1/3 Documentation/MyFirstContribution: recommend shallow threadingPatrick Steinhardt, Jun 3, 2026
  26. Tuomas AholaJun 3, 2026
  27. Patrick SteinhardtJun 8, 2026
  28. Weijie YuanJun 3, 2026
  29. Patrick SteinhardtJun 8, 2026
  30. Weijie YuanJun 8, 2026
  31. Kristoffer HaugsbakkJun 3, 2026
  32. Patrick SteinhardtJun 8, 2026
  33. 2/3 Documentation/MyFirstContribution: recommend the use of b4Patrick Steinhardt, Jun 3, 2026
  34. Toon ClaesJun 4, 2026
  35. Patrick SteinhardtJun 8, 2026
  36. 3/3 b4: introduce configuration for the Git projectPatrick Steinhardt, Jun 3, 2026
  37. Toon ClaesJun 3, 2026
  38. Patrick SteinhardtJun 8, 2026
  39. 0/3 Documentation: recommend the use of b4Patrick Steinhardt, Jun 8, 2026
  40. 1/3 MyFirstContribution: recommend shallow threading of cover lettersPatrick Steinhardt, Jun 8, 2026
  41. Karthik NayakJun 10, 2026
  42. Patrick SteinhardtJun 15, 2026
  43. 2/3 MyFirstContribution: recommend the use of b4Patrick Steinhardt, Jun 8, 2026
  44. 3/3 b4: introduce configuration for the Git projectPatrick Steinhardt, Jun 8, 2026
  45. Karthik NayakJun 10, 2026
  46. Patrick SteinhardtJun 15, 2026
  47. Toon ClaesJun 9, 2026
  48. Junio C HamanoJun 9, 2026
  49. Patrick SteinhardtJun 10, 2026
  50. 0/3 Documentation: recommend the use of b4Patrick Steinhardt, Jun 15, 2026
  51. 1/3 MyFirstContribution: recommend shallow threading of cover lettersPatrick Steinhardt, Jun 15, 2026
  52. 2/3 MyFirstContribution: recommend the use of b4Patrick Steinhardt, Jun 15, 2026
  53. 3/3 b4: introduce configuration for the Git projectPatrick Steinhardt, Jun 15, 2026
  54. Toon ClaesJun 16, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.