From: Joe Perches <joe@perches.com>
To: Allen Hubbe <allenbh@gmail.com>,
linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] checkpatch: check signoff when reading stdin
Date: Wed, 27 Jul 2016 17:41:54 -0700 [thread overview]
Message-ID: <1469666514.3998.14.camel@perches.com> (raw)
In-Reply-To: <5e6441a147be1d796620d1e302e1c73daa8c0b86.1469656370.git.allenbh@gmail.com>
> This change causes checkpatch to check for a missing signoff line, even
> if the filename is '-', as in the first variation of the command.
I think this is not a great idea because the most likely
use case is piping git diff output ala:
$ git diff <some_path> | ./scripts/checkpatch.pl -
next prev parent reply other threads:[~2016-07-28 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 23:05 Allen Hubbe
2016-07-28 0:41 ` Joe Perches [this message]
2016-07-29 14:45 ` Allen Hubbe
2016-07-29 15:38 ` Joe Perches
2016-07-28 1:53 ` [PATCH v2] " Allen Hubbe
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=1469666514.3998.14.camel@perches.com \
--to=joe@perches.com \
--cc=allenbh@gmail.com \
--cc=apw@canonical.com \
--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®