Date: Thu, 9 Mar 2017 21:36:50 +0100 (CET)
From: Julia Lawall <julia.lawall@lip6.fr>
To: Scott Branden <scott.branden@broadcom.com>
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
Subject: outreachy
Message-ID: <alpine.DEB.2.20.1703092133340.2306@hadrien>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 461
Lines: 13

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?

thanks,
julia