From: Mark Brown <broonie@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Joe Perches <joe@perches.com>,
Rob Herring <robherring2@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Leon Romanovsky <leon@kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev, tools@linux.kernel.org,
Simon Glass <sjg@chromium.org>
Subject: Re: Better tools for sending patches (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches)
Date: Fri, 23 Apr 2021 17:03:10 +0100 [thread overview]
Message-ID: <20210423160310.GD5507@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=Xi6TL05M2bYKNgNB-ePY40CvonPzJYeMhXMPGgYKA5_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Fri, Apr 23, 2021 at 07:52:30AM -0700, Doug Anderson wrote:
> I know it's nearly impossible to get people to change their workflows,
> but if you're open to it I definitely suggest giving it a try. Simon
> Glass (the original author) is also quite receptive to improvements.
I have something broadly similar (much more simplistic and overall less
capable) which I wrote myself - the things I have that this doesn't have
are:
- Attesting the outgoing patches with b4.
- Tagging the published series in git.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-23 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <afc5664dc2b60f912dd97abfa818b3f7c4237b92.camel@HansenPartnership.com>
[not found] ` <YID5xhy2vv45fnOv@unreal>
[not found] ` <20210422112001.22c64fe9@coco.lan>
[not found] ` <20210422125357.uuxprp6rqxewcdsr@nitro.local>
[not found] ` <YIG43TuqmxU24evq@unreal>
2021-04-22 18:05 ` backfilling threads with b4 (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches) Konstantin Ryabitsev
2021-04-22 18:51 ` Leon Romanovsky
2021-04-25 10:58 ` Leon Romanovsky
[not found] ` <YIFfXTVMDmHwVmSR@unreal>
[not found] ` <20210422092916.556e5e50@gandalf.local.home>
[not found] ` <CAL_JsqKS-=shqkLhzKeLHqNPhosGJw5X-fOi+dy1rT3Q_LfBZg@mail.gmail.com>
2021-04-23 6:04 ` [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches Mauro Carvalho Chehab
2021-04-23 6:46 ` Joe Perches
2021-04-23 7:13 ` Mauro Carvalho Chehab
2021-04-23 7:20 ` [PATCH RFC] scripts: add a script for sending patches Mauro Carvalho Chehab
2021-04-23 14:52 ` Better tools for sending patches (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches) Doug Anderson
2021-04-23 16:03 ` Mark Brown [this message]
2021-04-23 17:12 ` Leon Romanovsky
2021-04-26 23:50 ` Simon Glass
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=20210423160310.GD5507@sirena.org.uk \
--to=broonie@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dianders@chromium.org \
--cc=joe@perches.com \
--cc=ksummit@lists.linux.dev \
--cc=leon@kernel.org \
--cc=mchehab@kernel.org \
--cc=robherring2@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sjg@chromium.org \
--cc=tools@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