From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751378AbdBZUqJ (ORCPT ); Sun, 26 Feb 2017 15:46:09 -0500 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:29987 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751221AbdBZUqH (ORCPT ); Sun, 26 Feb 2017 15:46:07 -0500 X-IronPort-AV: E=Sophos;i="5.35,210,1484002800"; d="scan'208";a="262143745" Date: Sun, 26 Feb 2017 20:40:39 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: Joe Perches cc: Julia Lawall , Narcisa Ana Maria Vasile , swarren@wwwdotorg.org, lee@kernel.org, eric@anholt.net, f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com, daniel.baluta@spamfreegmail.com, gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com, bcm-kernel-feedback-list@broadcom.com, mzoran@crowfest.net, danielperezdeandres@gmail.com, dan.carpenter@oracle.com, devel@driverdev.osuosl.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' In-Reply-To: <1488137824.9188.7.camel@perches.com> Message-ID: References: <1488131271-2908-1-git-send-email-narcisaanamaria12@gmail.com> <1488134072.9188.3.camel@perches.com> <1488137824.9188.7.camel@perches.com> 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 wrote: > > > 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. > And the link you sent is for newbies, not for > outreachy. The link is part of the outreachy tutorial, which is hosted by the kernelnewbies website. julia > > The "don't cc lists" --nol use is inappropriate > there. > >