From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: linux-kernel@vger.kernel.org,
Bruce Allan <bruce.w.allan@intel.com>,
Anish Kumar <anish198519851985@gmail.com>,
Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] checkpatch: do not test/warn of leading whitespace before signature tags
Date: Thu, 18 Aug 2011 00:26:30 -0700 [thread overview]
Message-ID: <1313652390.32547.53.camel@Joe-Laptop> (raw)
In-Reply-To: <1313650112-17287-1-git-send-email-jeffrey.t.kirsher@intel.com>
On Wed, 2011-08-17 at 23:48 -0700, Jeff Kirsher wrote:
> From: Bruce Allan <bruce.w.allan@intel.com>
>
> Commit 2011247 introduced additional style checks for signature tags in
> patches which is good. Unfortunately, now whenever patches are checked
> by piping the output of 'git show' or 'stg show' through checkpatch it
> warns not to use whitespace before all signature tags since these (and the
> rest of the patch description) are indented. Remove this test/warning.
I think this is not a good idea.
checkpatch is meant for patches not git log output.
indenting signatures can cause other problems later.
I think you can avoid this easily by using checkpatch
option --ignore=BAD_SIGN_OFF when using git log output
as input.
You could also use:
git log --format="commit %H%nAuthor: %an <%ae>%nDate: %aD%n%n%s%n%n%b"
so that you get the current default --format=medium
output without indenting the commit log body.
next prev parent reply other threads:[~2011-08-18 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 6:48 [PATCH] checkpatch: do not test/warn of leading whitespace before signature tags Jeff Kirsher
2011-08-18 7:26 ` Joe Perches [this message]
2011-08-18 7:47 ` Jeff Kirsher
2011-08-18 7:59 ` Joe Perches
2011-08-18 8:07 ` Jeff Kirsher
2011-08-18 8:16 ` Joe Perches
2011-08-18 8:26 ` Jeff Kirsher
2011-08-18 8:31 ` Joe Perches
2011-08-18 8:43 ` Jeff Kirsher
2011-08-18 8:56 ` Joe Perches
2011-08-18 9:21 ` Jeff Kirsher
2011-08-18 8:16 ` Jeff Kirsher
2011-08-19 14:13 ` Michal Marek
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=1313652390.32547.53.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=anish198519851985@gmail.com \
--cc=apw@canonical.com \
--cc=bruce.w.allan@intel.com \
--cc=jeffrey.t.kirsher@intel.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