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

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

From
Patrick Steinhardt <ps@pks.im>
Date
Jun 8, 2026, 06:48 UTC
Message-ID
<aiZlx-ue6N8gCIMr@pks.im>
In-Reply-To
<87mrxa27xq.fsf@emacs.iotcl.com>
On Thu, Jun 04, 2026 at 07:25:37AM +0200, Toon Claes wrote:
Show 27 quoted lines
> Patrick Steinhardt <ps@pks.im> writes:
> > diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
> > index 069020196c..fc0b06ae67 100644
> > --- a/Documentation/MyFirstContribution.adoc
> > +++ b/Documentation/MyFirstContribution.adoc
> > @@ -833,7 +833,7 @@ This patchset is part of the MyFirstContribution tutorial and should not
> >  be merged.
> >  ----
> >  
> > -At this point the tutorial diverges, in order to demonstrate two
> > +At this point the tutorial diverges, in order to demonstrate three
> >  different methods of formatting your patchset and getting it reviewed.
> >  
> >  The first method to be covered is GitGitGadget, which is useful for those
> > @@ -845,9 +845,14 @@ more fine-grained control over the emails to be sent. This method requires some
> >  setup which can change depending on your system and will not be covered in this
> >  tutorial.
> >  
> > +The third method to be covered is `b4`, which builds on top of `git
> > +format-patch` and `git send-email`. This method is the recommended way to
> > +submit patches via mail as it automates a lot of the bookkeeping required by
> > +`git send-email`.
> 
> The GitGitGadget method includes Running CI, maybe that's worth
> mentioning the user is responsible themselves to run the whole test
> suite? Or is this outside the scope of this series, since `git
> send-email` doesn't include that too.
I'd say it's out-of-scope for this patch series.

That being said, I have been wondering last week whether we can automate running CI in some fashion to shorten feedback cycles, bridge the gap between the mailing list and CI and ultimately help both reviewers and Junio. Some subsystems in the Linux kernel for example have tooling that picks up patch series from the mailing list, runs it through CI and then reports results to the mailing list (for example [1]).

Having something like that might be valuable for us, too.
Patrick
[1]: https://github.com/linux-netdev/nipa
Previous: Toon ClaesNext: Patrick Steinhardt
Message 35 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.