public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Joe Perches <joe@perches.com>
Cc: jeffrey.t.kirsher@intel.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Allan, Bruce W" <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: Fri, 19 Aug 2011 16:13:10 +0200	[thread overview]
Message-ID: <4E4E6F76.8070508@suse.cz> (raw)
In-Reply-To: <1313654341.32547.62.camel@Joe-Laptop>

On 18.8.2011 09:59, Joe Perches wrote:
>>>> From: Bruce Allan <bruce.w.allan@intel.com>
>>>> 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 suppose checkpatch could have a different "--input=git"
> or some such to avoid certain things that git might produce
> that a patch would not.

One can also use 'git show --pretty=email', which does not do the
indentation.

Michal

      parent reply	other threads:[~2011-08-19 14:13 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
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 [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=4E4E6F76.8070508@suse.cz \
    --to=mmarek@suse.cz \
    --cc=anish198519851985@gmail.com \
    --cc=apw@canonical.com \
    --cc=bruce.w.allan@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=joe@perches.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