All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com,
	Don Slutz <dslutz@verizon.com>
Subject: Re: [PATCH for-4.5] scripts/get_maintainer.pl: Correctly CC the maintainers
Date: Thu, 20 Nov 2014 17:20:01 +0000	[thread overview]
Message-ID: <546E22C1.6050206@linaro.org> (raw)
In-Reply-To: <1416502667.21748.1.camel@citrix.com>

On 11/20/2014 04:57 PM, Ian Campbell wrote:
> On Thu, 2014-11-20 at 16:52 +0000, Ian Campbell wrote:
>> On Thu, 2014-11-20 at 16:43 +0000, Julien Grall wrote:
>>> On 11/20/2014 04:29 PM, Ian Campbell wrote:
>>>>> Forgot to add, the example above show the difference without and with
>>>>> the patch. The list is correct because both ARM and x86 maintainers
>>>>> should be CC. Because of this all "THE REST" maintainers are added.
>>>>
>>>> Just to be clear, you mean that everyone under THE REST is added solely
>>>> because they also happen to be maintainers of some other relevant bit of
>>>> code, not that THE REST is explicitly added in this case, right?
>>>
> 
> Just a small clarification...
> 
>>> Yes, my description was confusing. With setting $email_remove_duplicates
>>> to 0, the script will:
>>>    1) Append the list of maintainers for every file
> 
> At this point each maintainer remains associated with the role/reason
> they are added, right?

Yes. Every time the maintainers is listed we add in the list no matters
if the mail already exists. So the maintainers may be listed twice with
different roles (for instance: x86 and "THE REST").

>>>    2) Filter the list to remove the entry with "THE REST" role
> 
> And this only happens if there are roles other than "THE REST" in the
> list?

Yes.

> 
>>>    3) Remove duplicated address
>>>
>>> The previous behavior was:
>>>    1) Get the list of maintainers of the file (incidentally all the
>>> maintainers in "THE REST" role are added). If the email address already
>>> exists in the global list, skip it.
>>>    2) Filter the list to remove the entry with "THE REST" role
> 
> Whereas here the link from maintainer to the role is lost, hence
> everyone in THE REST is blindly removed?

Yes.

>>> So if a maintainers is marked on the "THE REST" on the first file and
>>> actually be an x86 maintainers on the second file, the scripts will only
>>> retain the "THE REST" role.
>>>
>>> If it's more clear, I can add the explanation above in the commit message.
>>
>> It is, please do.

I will send a new version.

Regards,


-- 
Julien Grall

  reply	other threads:[~2014-11-20 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 20:03 [PATCH for-4.5] scripts/get_maintainer.pl: Correctly CC the maintainers Julien Grall
2014-11-20 16:08 ` Ian Campbell
2014-11-20 16:15   ` Julien Grall
2014-11-20 16:21     ` Julien Grall
2014-11-20 16:29       ` Ian Campbell
2014-11-20 16:43         ` Julien Grall
2014-11-20 16:52           ` Ian Campbell
2014-11-20 16:57             ` Ian Campbell
2014-11-20 17:20               ` Julien Grall [this message]
2014-11-20 16:30     ` Ian Campbell
2014-11-20 17:20       ` Julien Grall

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=546E22C1.6050206@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.