public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jeffy <jeffy.chen@rock-chips.com>
To: Joe Perches <joe@perches.com>, linux-kernel@vger.kernel.org
Cc: briannorris@chromium.org, dianders@chromium.org
Subject: Re: [PATCH] get_maintainer: apply all .get_maintainer.ignore files
Date: Thu, 06 Apr 2017 09:16:16 +0800	[thread overview]
Message-ID: <58E596E0.80608@rock-chips.com> (raw)
In-Reply-To: <1491408412.27353.82.camel@perches.com>

Hi Joe,

On 04/06/2017 12:06 AM, Joe Perches wrote:
> On Wed, 2017-04-05 at 19:30 +0800, Jeffy Chen wrote:
>> Currently we are searching "./:$ENV{HOME}/:.scripts/" for ignore file,
>> but would always get "./.get_maintainer.ignore" only.
>
> That's the point.
>
> It allows you to have specific .ignore files for various projects.
yes, but we now have a .get_maintainer.ignore tracked in kernel's git 
repository:
kernel# git log --oneline .get_maintainer.ignore
e525293 Add hch to .get_maintainer.ignore

so if we wanna modify the ignore list locally, we would have to do it 
every time reset the repository.
>
>> This patch applies all .get_maintainer.ignore, so it would be easier to
>> add ignore list locally.
>
> Why stack?  What's the value in that?
>
i found some mail server(for example chinese 263) would refuse to send 
mails when any of the addresses are invalid. so i need to add them to 
the ignore list(for example Yakir Yang <ykk@rock-chips.com>).

i think it would be good if we can provide a way to modify local ignore 
list without affecting the repository.

or maybe i should just send my ignore file upstream?
>
>
>

  reply	other threads:[~2017-04-06  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 11:30 [PATCH] get_maintainer: apply all .get_maintainer.ignore files Jeffy Chen
2017-04-05 16:06 ` Joe Perches
2017-04-06  1:16   ` jeffy [this message]
2017-04-06  1:21     ` Joe Perches

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=58E596E0.80608@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=briannorris@chromium.org \
    --cc=dianders@chromium.org \
    --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