From mboxrd@z Thu Jan 1 00:00:00 1970 From: joe@perches.com (Joe Perches) Date: Sun, 26 Feb 2017 13:56:51 -0800 Subject: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' In-Reply-To: References: <1488131271-2908-1-git-send-email-narcisaanamaria12@gmail.com> <1488134072.9188.3.camel@perches.com> <1488137824.9188.7.camel@perches.com> Message-ID: <1488146211.9188.10.camel@perches.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > On Sun, 26 Feb 2017, Joe Perches wrote: > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > Mailing lists _should_ be copied on patch submissions. > > > The idea of outreachy is that it should be a place for people to get > > > started without too much criticism from the outside. Originally, only the > > > outreachy mailing list received patches. But staging maintainers were > > > confused to have their drivers receiving patches that they had not seen. > > > So we expanded it to maintainers. > > > > That also doesn't make much sense as patches > > should not be applied that have not reached > > a mailing list for review. > > > > As long as initial outreachy patches are not > > applied and are just for internal review by > > any outside person but the outreachy list and > > are not be applied by maintainers, then perhaps > > it's best if neither maintainers nor lists are > > cc'd on the patches. > > The patches are applied by Greg. Greg suggested the policy of adding > maintainers but not including mailing lists. I'll let him consider > whether the policy should be changed. Well, I will comment on patches sent to the kernel list. I'm not subscribed to outreachy and I don't want to be subscribed to that list either.