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:30:18 +0000 [thread overview]
Message-ID: <1416501018.20161.5.camel@citrix.com> (raw)
In-Reply-To: <546E1389.1070304@linaro.org>
On Thu, 2014-11-20 at 16:15 +0000, Julien Grall wrote:
> Hi Ian,
>
> On 11/20/2014 04:08 PM, Ian Campbell wrote:
> > On Tue, 2014-11-18 at 20:03 +0000, Julien Grall wrote:
> >> By default, the script get_maintainer.pl will remove duplicates email as soon
> >> as it appends the list of maintainers of a new file, and therefore override
> >> the role of the developper.
> >>
> >> On complex patch (see [1]), this will result to ommitting randomly some
> >> maintainers.
> >>
> >> This could be fixed
> >
> > Are you proposing an alternative/better fix here? or describing what
> > this patch does?
>
> Describing what the patch does.
Then I think you meant "This is fixed" or "This patches fixes this
by ...".
> By drawbacks I meant, if there is another bug in the script then we may
> end up to cc too many people. Honestly I don't believe it's the case.
Sure, lets assume not.
Ian
next prev parent reply other threads:[~2014-11-20 16:34 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
2014-11-20 16:30 ` Ian Campbell [this message]
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=1416501018.20161.5.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.