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

Re: [PATCH 1/2] b4: introduce configuration for the Git project

From
Patrick Steinhardt <ps@pks.im>
Date
Jun 2, 2026, 14:56 UTC
Message-ID
<ah7vKc8XTKdpcHuH@pks.im>
In-Reply-To
<xmqqldcxvziw.fsf@gitster.g>
On Tue, Jun 02, 2026 at 10:32:23PM +0900, Junio C Hamano wrote:
Show 30 quoted lines
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > We're about to extend our documentation to recommend b4 for sending
> > patch series ot the mailing list. Prepare for this by introducing a b4
> > configuration so that the tool knows to honor our preferences. For now,
> > this configuration does two things:
> >
> >   - It configures "send-same-thread = shallow", which tells b4 to always
> >     send subsequent versions of the same patch series as a reply to the
> >     cover letter of the first version.
> >
> >   - It configures "prep-cover-template", which tells b4 to use a custom
> >     template for the cover letter. The most important change compared to
> >     the default template is that our custom template also includes a
> >     range-diff.
> >
> > There's potentially more things that we may want to configure going
> > forward, like for example auto-configuration of folks to Cc on certain
> > patches. But these two tweaks feel like a good place to start.
> >
> > Signed-off-by: Patrick Steinhardt <ps@pks.im>
> > ---
> >  .b4-config         |  3 +++
> >  .b4-cover-template | 11 +++++++++++
> >  2 files changed, 14 insertions(+)
> 
> Shipping a sample like ".b4-config.sample" that users who opt-in can
> copy-and-edit into the final name ".b4-config" is OK, but I'd rather
> not to ship the configuration files that the users would want to edit
> (hence making the tree dirty).

I think shipping this as-is makes sense though, as it allows us to make b4 behave the way we want it to without the user having to do anything. If users actually want to reconfigure those values they can by saying `git config set b4.<foobar>`, as the repository-local configuration will override whatever `.b4-config` has.

Patrick
Previous: Junio C HamanoNext: Ramsay Jones
Message 4 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.