From: Julia Lawall <julia.lawall@lip6.fr>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Scott Branden <scott.branden@broadcom.com>,
Julia Lawall <julia.lawall@lip6.fr>,
lee@kernel.org, eric@anholt.net, f.fainelli@gmail.com,
rjui@broadcom.com, sbranden@broadcom.com,
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: Re: outreachy
Date: Fri, 17 Mar 2017 17:55:42 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703171753550.4098@hadrien> (raw)
In-Reply-To: <20170317152519.GA8684@amd>
On Fri, 17 Mar 2017, Pavel Machek wrote:
> Hi!
>
> >
> > Hah! That's the joy of being a maintainer of a driver in staging. Even
> > if you filter out outreachy, you are going to get a lot of "basic
> > mistakes" and other type patches cc:ed to you.
> >
> > I strongly suggest, that if you all don't like this type of stuff,
> > either:
> > - work to get the code out of staging as soon as possible (i.e.
> > send me coding style fixes for everything right now, and then
> > fix up the rest of the stuff.)
> > - take yourself off the maintainer list for this code.
> >
> > It's your choice, outreachy right now is a lot of patches, but again,
> > it's not going to keep you from getting the "basic" stuff sent to you
> > in ways that is totally wrong.
>
> Could we get these trivial patches off the lkml? Yes, lkml already has
> a lot of traffic, but no, this is not useful :-(.
The outreachy instructions say to use the -nol argument to
get_maintainers, which would prevent them from being sent to any mailing
list. However others thought that all patches should be sent to mailing
lists, and so I haven't enforced anything for people who have omitted
-nol. However I have tried to remove bcm maintainers from CC lists on
replies and reminded people not to send you patches,
julia
>
> Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>
next prev parent reply other threads:[~2017-03-17 16:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 20:36 outreachy Julia Lawall
2017-03-09 20:51 ` outreachy Scott Branden
2017-03-09 20:56 ` outreachy Stephen Warren
2017-03-09 21:20 ` outreachy Greg KH
2017-03-09 22:15 ` outreachy Florian Fainelli
2017-03-10 6:01 ` outreachy Greg KH
2017-03-17 15:25 ` outreachy Pavel Machek
2017-03-17 16:55 ` Julia Lawall [this message]
2017-03-20 10:20 ` outreachy Pavel Machek
2017-03-20 10:30 ` outreachy Greg KH
2017-03-20 16:14 ` outreachy Pavel Machek
2017-03-19 7:37 ` outreachy/moving a driver out of staging Michael Zoran
2017-03-19 9:15 ` Russell King - ARM Linux
2017-03-19 10:22 ` Michael Zoran
2023-03-15 13:17 Outreachy Menna Mahmoud
2023-03-15 14:03 ` Outreachy Dan Carpenter
2023-03-15 19:24 ` Outreachy Randy Dunlap
2023-03-15 20:09 ` Outreachy Lars-Peter Clausen
2023-03-19 11:20 ` Outreachy Menna Mahmoud
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.1703171753550.4098@hadrien \
--to=julia.lawall@lip6.fr \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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=pavel@ucw.cz \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=scott.branden@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®