All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
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 16:52:02 +0000	[thread overview]
Message-ID: <1416502322.20161.9.camel@citrix.com> (raw)
In-Reply-To: <546E1A18.1040606@linaro.org>

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?
> 
> Yes, my description was confusing. With setting $email_remove_duplicates
> to 0, the script will:
>    1) Append the list of maintainers for every file
>    2) Filter the list to remove the entry with "THE REST" role
>    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
> 
> 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.

Ian.

  reply	other threads:[~2014-11-20 16:52 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 [this message]
2014-11-20 16:57             ` Ian Campbell
2014-11-20 17:20               ` Julien Grall
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=1416502322.20161.9.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@linaro.org \
    --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.