Subject: Re: outreachy
To: Julia Lawall <julia.lawall@lip6.fr>
References: <alpine.DEB.2.20.1703092133340.2306@hadrien>
Cc: swarren@wwwdotorg.org, lee@kernel.org, eric@anholt.net,
        f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
        gregkh@linuxfoundation.org, bcm-kernel-feedback-list@broadcom.com,
        devel@driverdev.osuosl.org, linux-rpi-kernel@lists.infradead.org,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
From: Scott Branden <scott.branden@broadcom.com>
Message-ID: <443f0143-aec1-2559-a2c2-73b245632948@broadcom.com>
Date: Thu, 9 Mar 2017 12:51:13 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1703092133340.2306@hadrien>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 837
Lines: 24

Hi Julia,

On 17-03-09 12:36 PM, Julia Lawall wrote:
> Hello,
>
> I discussed the issue of outreachy patches for bcm with Greg, and we are
> not convinced that not having the patches CCd to you is such a good idea.
> While we don't want to spam you with noise, some of the applicants are
> starting to make more significant changes that it could be useful for you
> to be aware of.
>
> Could we try a compromise where you are not CCd on whitespace patches, but
> you are CCd on patches that actually modify the code?
All I'm asking is you work through your outreachy patches internal first 
to get rid of the most basic mistakes and email traffic it is geerating. 
  Once that learning process is through then they can be sent out like 
any other patches to the kernel mailing lists and maintainers.
>
> thanks,
> julia
>

Thanks,
Scott