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

Re: Review process improvements

From
SHStefan Hajnoczi <stefanha@redhat.com>
Date
Dec 23, 2021, 13:50 UTC
Message-ID
<YcR+rZ7YznQlTuRf@stefanha-x1.localdomain>
In-Reply-To
<20211217183942.npvkb3ajnx6p5cbp@meerkat.local>
> I'd like to also mention that I'm hoping to add a few more features to b4 that
> will hopefully improve the patch submission process for folks.

This looks excellent! I wanted to mention a few features that have been popular in the git-publish patch series management tool (https://github.com/stefanha/git-publish/) in case you want to include something similar in b4:

- "Profiles" (.gitpublishprofile or stored in .git/config) with To and
  CC addresses, --subject-prefix, cover letter templates, etc. The
  default profile is automatically loaded when you run "git publish". If
  the git repo you're working on includes a default profile then you
  don't need to specify any command-line options to send a correctly
  formatted patch series to the maintainers! A great help for one-off
  contributors but also a time-saver for regular contributors.
- An interactive mode that lets you inspect the final patch series and
  edit the CC list. Avoids mistakes and embarassment :).
- Saving the CC list between revisions (v2, v3, etc).
- Sending pull requests (for sub-maintainers) because there are times
  when pull requests also need a v2 or even a v3 ;). The workflow is
  basically the same as sending patch series.
- githooks(5) before sending patches series and pull requests. Useful
  for coding style and patch series linters.

The git-publish man page is here if you want to read more: https://github.com/stefanha/git-publish/blob/master/git-publish.pod#quickstart

Stefan
Previous: Junio C HamanoNext: Ævar Arnfjörð Bjarmason
Message 14 of 22 in “Review process improvements”
  1. Emily ShafferDec 16, 2021
  2. rsbecker@nexbridge.comDec 16, 2021
  3. Junio C HamanoDec 17, 2021
  4. Konstantin RyabitsevDec 17, 2021
  5. Christian CouderDec 20, 2021
  6. Mark BrownDec 20, 2021
  7. Ævar Arnfjörð BjarmasonDec 22, 2021
  8. Fabian StelzerDec 22, 2021
  9. Konstantin RyabitsevDec 22, 2021
  10. Junio C HamanoDec 22, 2021
  11. Konstantin RyabitsevDec 22, 2021
  12. Why GitGitGadget does not use Sender:, was Re: Review process improvementsJohannes Schindelin, Jan 10, 2022
  13. Junio C HamanoJan 10, 2022
  14. Stefan HajnocziDec 23, 2021
  15. Ævar Arnfjörð BjarmasonDec 20, 2021
  16. Eric SunshineDec 20, 2021
  17. João Victor BonfimDec 20, 2021
  18. Emily ShafferJan 5, 2022
  19. João Victor BonfimJan 9, 2022
  20. brian m. carlsonDec 21, 2021
  21. Emily ShafferJan 5, 2022
  22. Matthias AßhauerJan 9, 2022

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.