public inbox for linux-kernel@vger.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>
Subject: Re: [PATCH -next] get_maintainer: Improve "Author:" rolestats
Date: Tue, 05 Nov 2013 14:01:47 +0800	[thread overview]
Message-ID: <527889CB.50807@asianux.com> (raw)
In-Reply-To: <1383630652.4387.8.camel@joe-AO722>

On 11/05/2013 01:50 PM, Joe Perches wrote:
> On Tue, 2013-11-05 at 13:42 +0800, Chen Gang wrote:
>> On 11/05/2013 01:23 PM, Joe Perches wrote:
>>> On Tue, 2013-11-05 at 10:37 +0800, Chen Gang wrote:
> 
>> (if so, it seems the related
>> patch need be re-committed again by the related author).
> 
> No it doesn't mean that.
> 
> Prior to this patch, get_maintainer only used "sign-off-by"
> style lines to find interested parties to send patches to
> when the MAINTAINERS file did not have a specific section
> entry with a matching file pattern to the files that that
> the patch modified.
> 
> And there was a defect in the script when no commit history
> at all was found for the files modified during the period
> selected (1 year of git log history by default)
> 
> Now, using this newly modified get_maintainer.pl script,
> the commit authors shown in the git log history as well as
> the commit signers are selected.
> 
> If there is no git history, the script defect is also fixed.
> 

Yeah, our "get_maintainer.pl" need be smart enough to bear it (this
patch let our "get_maintainer.pl" smart enough).

But for this kind of patch, need it re-commit again? (for me, I
recommend to re-commit it again by the related author).


Thanks.
-- 
Chen Gang

      reply	other threads:[~2013-11-05  6:02 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
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 [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=527889CB.50807@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 \
    /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