From: Stefan Hajnoczi <stefanha@redhat.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Emily Shaffer <emilyshaffer@google.com>,
git@vger.kernel.org, jrnieder@gmail.com,
jonathantanmy@google.com, steadmon@google.com,
chooglen@google.com, calvinwan@google.com,
workflows@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>
Subject: Re: Review process improvements
Date: Thu, 23 Dec 2021 13:50:37 +0000 [thread overview]
Message-ID: <YcR+rZ7YznQlTuRf@stefanha-x1.localdomain> (raw)
In-Reply-To: <20211217183942.npvkb3ajnx6p5cbp@meerkat.local>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-12-23 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YbvBvch8JcHED+A9@google.com>
2021-12-17 18:39 ` Konstantin Ryabitsev
2021-12-20 10:48 ` Christian Couder
2021-12-20 12:29 ` Mark Brown
2021-12-22 3:26 ` Ævar Arnfjörð Bjarmason
2021-12-22 13:07 ` Fabian Stelzer
2021-12-22 15:45 ` Konstantin Ryabitsev
2021-12-22 19:42 ` Junio C Hamano
2021-12-22 21:32 ` Konstantin Ryabitsev
2022-01-10 13:03 ` Why GitGitGadget does not use Sender:, was " Johannes Schindelin
2022-01-10 17:13 ` Junio C Hamano
2021-12-23 13:50 ` Stefan Hajnoczi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YcR+rZ7YznQlTuRf@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=calvinwan@google.com \
--cc=chooglen@google.com \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=steadmon@google.com \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox