All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Joe Perches <joe@perches.com>
Cc: Chen Gang F T <chen.gang.flying.transformer@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Subject: Re: [PATCH -next] get_maintainer: Improve "Author:" rolestats
Date: Tue, 05 Nov 2013 14:04:00 +0800	[thread overview]
Message-ID: <52788A50.6000403@asianux.com> (raw)
In-Reply-To: <1383630867.4387.11.camel@joe-AO722>

On 11/05/2013 01:54 PM, Joe Perches wrote:
> On Tue, 2013-11-05 at 13:45 +0800, Chen Gang wrote:
>> > If really as what I guess above (some patches no Signed-of-by), is there
>> > a tool to check and find this issue in time?
> scripts/checkpatch.pl bleats a message on missing sign-offs.

Yeah, the author/maintainer can use it for checking.

But do we have additional tools to let the version tree integrator (e.g.
sfr) notice about it?


Thanks.
-- 
Chen Gang

  reply	other threads:[~2013-11-05  6:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 11:20 [Suggestion] about latest commit for "scripts/get_maintainers.pl" Chen Gang
2013-11-01 18:32 ` Joe Perches
2013-11-02 14:07   ` Chen Gang F T
2013-11-04 21:54     ` [PATCH -next] get_maintainer: Improve "Author:" rolestats Joe Perches
2013-11-05  2:22       ` Chen Gang
2013-11-05  2:37         ` Chen Gang
2013-11-05  5:23           ` Joe Perches
2013-11-05  5:42             ` Chen Gang
2013-11-05  5:45               ` Chen Gang
2013-11-05  5:54                 ` Joe Perches
2013-11-05  6:04                   ` Chen Gang [this message]
2013-11-05  6:16                     ` Joe Perches
2013-11-05  6:36                       ` Chen Gang
2013-11-05  5:50               ` Joe Perches
2013-11-05  6:01                 ` Chen Gang

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=52788A50.6000403@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=akpm@linux-foundation.org \
    --cc=chen.gang.flying.transformer@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.