From: Julia Lawall <julia.lawall@lip6.fr> To: Joe Perches <joe@perches.com> Cc: Julia Lawall <julia.lawall@lip6.fr>, Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com>, 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 '&' Date: Sun, 26 Feb 2017 20:40:39 +0100 (CET) [thread overview] Message-ID: <alpine.DEB.2.20.1702262038560.2056@hadrien> (raw) In-Reply-To: <1488137824.9188.7.camel@perches.com> 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. > >
WARNING: multiple messages have this Message-ID (diff)
From: julia.lawall@lip6.fr (Julia Lawall) To: linux-arm-kernel@lists.infradead.org Subject: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' Date: Sun, 26 Feb 2017 20:40:39 +0100 (CET) [thread overview] Message-ID: <alpine.DEB.2.20.1702262038560.2056@hadrien> (raw) In-Reply-To: <1488137824.9188.7.camel@perches.com> 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. > >
next prev parent reply other threads:[~2017-02-26 19:40 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-26 17:47 [PATCH] staging: bcm2835-audio: Fixed spacing around '&' Narcisa Ana Maria Vasile 2017-02-26 17:47 ` Narcisa Ana Maria Vasile 2017-02-26 18:03 ` [Outreachy kernel] " Julia Lawall 2017-02-26 18:03 ` Julia Lawall 2017-02-26 18:34 ` Joe Perches 2017-02-26 18:34 ` Joe Perches 2017-02-26 18:59 ` Julia Lawall 2017-02-26 18:59 ` Julia Lawall 2017-02-26 19:37 ` Joe Perches 2017-02-26 19:37 ` Joe Perches 2017-02-26 19:40 ` Julia Lawall [this message] 2017-02-26 19:40 ` Julia Lawall 2017-02-26 21:56 ` Joe Perches 2017-02-26 21:56 ` Joe Perches 2017-02-27 0:08 ` Scott Branden 2017-02-27 0:08 ` Scott Branden 2017-02-27 6:25 ` Julia Lawall 2017-02-27 6:25 ` Julia Lawall 2017-02-27 14:44 ` Dan Carpenter 2017-02-27 14:44 ` Dan Carpenter 2017-02-27 20:35 ` Scott Branden 2017-02-27 20:35 ` Scott Branden 2017-02-27 20:47 ` Michael Zoran 2017-02-27 20:47 ` Michael Zoran
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=alpine.DEB.2.20.1702262038560.2056@hadrien \ --to=julia.lawall@lip6.fr \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=dan.carpenter@oracle.com \ --cc=daniel.baluta@spamfreegmail.com \ --cc=danielperezdeandres@gmail.com \ --cc=devel@driverdev.osuosl.org \ --cc=eric@anholt.net \ --cc=f.fainelli@gmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=joe@perches.com \ --cc=lee@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=mzoran@crowfest.net \ --cc=narcisaanamaria12@gmail.com \ --cc=outreachy-kernel@googlegroups.com \ --cc=rjui@broadcom.com \ --cc=sbranden@broadcom.com \ --cc=swarren@wwwdotorg.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: linkBe 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.