From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: use patch subject when reading from stdin
Date: Tue, 15 Oct 2019 08:50:00 -0700 [thread overview]
Message-ID: <e09057e0eefb221549ef9686826e2d190ef36a9c.camel@perches.com> (raw)
In-Reply-To: <CAMuHMdWSGzs7BHqeHC0W5qUEpYqJ8B3Os4wdY11JNzt5+xEaiQ@mail.gmail.com>
On Tue, 2019-10-15 at 08:49 +0200, Geert Uytterhoeven wrote:
> Hi Joe,
Rehi Geert.
> On Mon, Oct 14, 2019 at 4:48 PM Joe Perches <joe@perches.com> wrote:
> > On Mon, 2019-10-14 at 11:20 +0200, Geert Uytterhoeven wrote:
[]
> > > I gave your solution a try.
> > > It only enables the reset-on-next-patch feature when using stdin.
> > > Thanks to the printed subject, it's now obvious to which patch a
> > > message applies to.
> > > However, the output is significantly different than when passing
> > > a split patch series. Can this be improved upon?
> > >
> > > Note that the only reason I'm using stdin is that I use formail to split
> > > a bundle in individual patches. Once checkpatch supports bundles (or
> > > mboxes) containing multiple patches, there's no longer a need for
> > > using formail, and the reset-on-next-patch feature should be
> > > enabled unconditionally.
> >
> > Using your collection of little tools idea,
> > why not write a trivial script like:
> >
> > grep "^Subject:" $1
> > checkpatch.pl $1
> >
> > and use that as the command line for formail
> > instead of adding unnecessary complexity to
> > checkpatch?
>
> That would be another possibility.
>
> But given more maintainers are starting to apply patchwork bundles (cfr.
> the workflows discussions), it makes sense to make their lives easier.
But given this particular change only works for stdin, then this
patch splitting idea wouldn't generically work.
> This is also useful for maintainers who save all patches to apply into a
> single mbox, and run checkpatch+git-am on that.
Which also wouldn't generally work for checkpatch <mbox>
> Summarized: git-am handles multiple patches, checkpatch requires
> splitting.
I still think it's better to introduce YA script that disaggregates
aggregated patches/emails and feeds each individual patch to
checkpatch rather than making checkpatch learn how to disaggregate.
Using "git mailsplit" as part of some additional script could work.
next prev parent reply other threads:[~2019-10-15 15:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 9:40 Geert Uytterhoeven
2019-10-08 12:50 ` Joe Perches
2019-10-08 12:59 ` Geert Uytterhoeven
2019-10-08 15:20 ` Joe Perches
2019-10-08 15:28 ` Geert Uytterhoeven
2019-10-08 17:02 ` Joe Perches
2019-10-08 18:10 ` Geert Uytterhoeven
2019-10-08 18:25 ` Joe Perches
2019-10-08 18:39 ` Geert Uytterhoeven
2019-10-08 18:50 ` Joe Perches
2019-10-14 9:20 ` Geert Uytterhoeven
2019-10-14 14:48 ` Joe Perches
2019-10-15 6:49 ` Geert Uytterhoeven
2019-10-15 15:50 ` Joe Perches [this message]
2019-10-15 16:40 ` Geert Uytterhoeven
2019-10-15 17:24 ` Joe Perches
2019-10-16 6:57 ` Geert Uytterhoeven
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=e09057e0eefb221549ef9686826e2d190ef36a9c.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®