tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
	Doug Anderson <dianders@chromium.org>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Joe Perches <joe@perches.com>,
	 Rob Herring <robherring2@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	 James Bottomley <James.Bottomley@hansenpartnership.com>,
	ksummit@lists.linux.dev,  tools@linux.kernel.org
Subject: Re: Better tools for sending patches (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches)
Date: Tue, 27 Apr 2021 09:50:51 +1000	[thread overview]
Message-ID: <CAPnjgZ2iiv-M3M8MaVFxQzHrT5jhL+YhPv+COxRMjCVU_OAS9w@mail.gmail.com> (raw)
In-Reply-To: <YIMAAFCe5N7ORNRX@unreal>

Hi,

The docs are on github also :
https://github.com/siemens/u-boot/blob/master/tools/patman/README

I find it relatively easy to update each patch with a little change
log as I change it. Then I know that when I type 'patman send' it will
do the right thing.

If people have workflows that would benefit from patman's help, but
need it to do an extra thing, I certainly accept patches to the tool.

Regards,
Simon

On Sat, 24 Apr 2021 at 03:12, Leon Romanovsky <leon@kernel.org> wrote:
>
> On Fri, Apr 23, 2021 at 05:03:10PM +0100, Mark Brown wrote:
> > 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.
>
> I have something similar too, which actually wrapper over git format-patch
> that properly set target (net-next, rdma-next, iproute2, rdma-core, mlx5-next
> e.t.c) and changes "To;" based on target.
>
> Thanks

      reply	other threads:[~2021-04-26 23:51 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
2021-04-23 17:12                     ` Leon Romanovsky
2021-04-26 23:50                       ` Simon Glass [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=CAPnjgZ2iiv-M3M8MaVFxQzHrT5jhL+YhPv+COxRMjCVU_OAS9w@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=broonie@kernel.org \
    --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=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;
as well as URLs for NNTP newsgroup(s).