From: "Mark Brown" <broonie@kernel.org>
To: tools@linux.kernel.org, James.Bottomley@HansenPartnership.com
Cc: toke@toke.dk,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@linux.kernel.org, Jens Axboe <axboe@kernel.dk>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [tools] [kernel.org users] b4: encouraging using the cover letter in merge commits?
Date: Mon, 21 Dec 2020 17:34:59 +0000 [thread overview]
Message-ID: <20201221173459.GB4521@sirena.org.uk> (raw)
In-Reply-To: <fc05bad0b5517500e62b271b8896f142060b235e.camel@HansenPartnership.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Sat, Dec 19, 2020 at 09:03:36AM -0800, James Bottomley wrote:
> I've got to say that creating a spurious merge for the cover letter
> looks even more tortuous than creating an empty commit. What
> advantages does this have over the existing link tag practice which is
> the one that we now use instead of the empty commit?
My scripting will apply serieses as branches and then record the cover
letter in the merge, I don't do this so much for recording the cover as
for the benefit of my testing - I tend to queue up things to apply and
then later have automation run through and check things before actually
merging them (anything without a cover latter gets dropped into a single
series together). Each series gets branched off separately and then
gets merged into the branch once I'm happy with the testing. By
splitting things out like this I'm helping ensure that if a patch has
problems it only causes issues on the individual series and there's less
stuff to to pick through and redo in case of problems.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
prev parent reply other threads:[~2020-12-21 17:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 21:32 b4: encouraging using the cover letter in merge commits? Toke Høiland-Jørgensen
2020-12-18 22:09 ` Konstantin Ryabitsev
2020-12-19 12:29 ` Toke Høiland-Jørgensen
2020-12-18 22:38 ` [kernel.org users] " James Bottomley
2020-12-19 12:34 ` Toke Høiland-Jørgensen
2020-12-19 17:03 ` James Bottomley
2020-12-19 17:21 ` Jakub Kicinski
2020-12-19 17:32 ` James Bottomley
2020-12-21 19:05 ` Jason Gunthorpe
2020-12-21 21:13 ` Michal Kubeček
2020-12-21 21:30 ` Arnaldo Carvalho de Melo
2020-12-22 6:30 ` Leon Romanovsky
2020-12-22 8:14 ` Geert Uytterhoeven
2020-12-22 12:36 ` Leon Romanovsky
2021-01-05 13:38 ` Jason Gunthorpe
2020-12-19 18:45 ` Jonathan Corbet
2020-12-19 18:49 ` James Bottomley
2020-12-19 18:57 ` Jonathan Corbet
2020-12-19 19:03 ` James Bottomley
2020-12-19 20:48 ` Arnaldo Carvalho de Melo
2020-12-19 21:01 ` James Bottomley
2020-12-19 21:43 ` Arnaldo Carvalho de Melo
2020-12-19 21:57 ` James Bottomley
2020-12-19 22:17 ` Arnaldo Carvalho de Melo
2020-12-19 23:34 ` James Bottomley
2020-12-21 17:34 ` Mark Brown [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=20201221173459.GB4521@sirena.org.uk \
--to=broonie@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=acme@kernel.org \
--cc=axboe@kernel.dk \
--cc=konstantin@linuxfoundation.org \
--cc=toke@toke.dk \
--cc=tools@linux.kernel.org \
--cc=users@linux.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).