workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
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
Subject: Re: Review process improvements
Date: Mon, 20 Dec 2021 12:29:34 +0000	[thread overview]
Message-ID: <YcB3LtxkItDVa2zd@sirena.org.uk> (raw)
In-Reply-To: <20211217183942.npvkb3ajnx6p5cbp@meerkat.local>

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]

On Fri, Dec 17, 2021 at 01:39:42PM -0500, Konstantin Ryabitsev wrote:

> 2. b4 submit --send: will generate a patch series from any commits created
>    from the topical branch fork point and use the cover letter from the
>    previous step. It will be able to send the patches using the traditional
>    SMTP way, OR it will allow using a web-based submission service I'm setting
>    up at kernel.org:

One thing my equivalent of this does (I might've used patman but I don't
think I was aware of it at the time) is to tag each revision as it's
published, might be worth considering.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-12-20 12:29 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 ` Review process improvements Konstantin Ryabitsev
2021-12-20 10:48   ` Christian Couder
2021-12-20 12:29   ` Mark Brown [this message]
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

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=YcB3LtxkItDVa2zd@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=calvinwan@google.com \
    --cc=chooglen@google.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;
as well as URLs for NNTP newsgroup(s).