All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Branden <scott.branden@broadcom.com>
To: Julia Lawall <julia.lawall@lip6.fr>
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: Re: outreachy
Date: Thu, 9 Mar 2017 12:51:13 -0800	[thread overview]
Message-ID: <443f0143-aec1-2559-a2c2-73b245632948@broadcom.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1703092133340.2306@hadrien>

Hi Julia,

On 17-03-09 12:36 PM, Julia Lawall wrote:
> 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?
All I'm asking is you work through your outreachy patches internal first 
to get rid of the most basic mistakes and email traffic it is geerating. 
  Once that learning process is through then they can be sent out like 
any other patches to the kernel mailing lists and maintainers.
>
> thanks,
> julia
>

Thanks,
Scott

WARNING: multiple messages have this Message-ID (diff)
From: scott.branden@broadcom.com (Scott Branden)
To: linux-arm-kernel@lists.infradead.org
Subject: outreachy
Date: Thu, 9 Mar 2017 12:51:13 -0800	[thread overview]
Message-ID: <443f0143-aec1-2559-a2c2-73b245632948@broadcom.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1703092133340.2306@hadrien>

Hi Julia,

On 17-03-09 12:36 PM, Julia Lawall wrote:
> 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?
All I'm asking is you work through your outreachy patches internal first 
to get rid of the most basic mistakes and email traffic it is geerating. 
  Once that learning process is through then they can be sent out like 
any other patches to the kernel mailing lists and maintainers.
>
> thanks,
> julia
>

Thanks,
Scott

  reply	other threads:[~2017-03-09 20:52 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 20:36 outreachy Julia Lawall
2017-03-09 20:36 ` outreachy Julia Lawall
2017-03-09 20:51 ` Scott Branden [this message]
2017-03-09 20:51   ` outreachy Scott Branden
2017-03-09 20:56   ` outreachy Stephen Warren
2017-03-09 20:56     ` outreachy Stephen Warren
2017-03-09 21:20     ` outreachy Greg KH
2017-03-09 21:20       ` outreachy Greg KH
2017-03-09 22:15       ` outreachy Florian Fainelli
2017-03-09 22:15         ` outreachy Florian Fainelli
2017-03-10  6:01         ` outreachy Greg KH
2017-03-10  6:01           ` outreachy Greg KH
2017-03-17 15:25       ` outreachy Pavel Machek
2017-03-17 15:25         ` outreachy Pavel Machek
2017-03-17 16:55         ` outreachy Julia Lawall
2017-03-17 16:55           ` outreachy Julia Lawall
2017-03-20 10:20           ` outreachy Pavel Machek
2017-03-20 10:20             ` outreachy Pavel Machek
2017-03-20 10:30             ` outreachy Greg KH
2017-03-20 10:30               ` outreachy Greg KH
2017-03-20 16:14               ` outreachy Pavel Machek
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  7:37         ` Michael Zoran
2017-03-19  9:15         ` Russell King - ARM Linux
2017-03-19  9:15           ` Russell King - ARM Linux
2017-03-19 10:22           ` Michael Zoran
2017-03-19 10:22             ` Michael Zoran
  -- strict thread matches above, loose matches on Subject: below --
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
2023-03-07 12:25 Outreachy Menna Mahmoud
2023-03-07 16:05 ` Outreachy Alison Schofield
2020-10-15  7:03 Outreachy Zodwa Phakathi
     [not found] <CAAe2+-RUhQDuw2kR4xCh2Sjh0CvpuBsWtK2iLmHih1iWtcP60w@mail.gmail.com>
2019-10-07 20:36 ` Outreachy Emily Shaffer
2019-10-08  8:27   ` Outreachy Johannes Schindelin
2016-09-30 20:40 outreachy Julia Lawall
2016-10-01  4:04 ` outreachy Rehas Sachdeva
2016-10-01  7:51 ` outreachy keila novo
2016-10-01  8:41 ` outreachy Bhumika Goyal
2016-10-01 18:18 ` outreachy Namrata A Shettar
2016-10-03  9:27 ` outreachy Georgiana Chelu
     [not found] <CACEff1gwioYfk=9wfUtPfDEpuK0CULw3iQBhtyj0CrLfC4VAuQ@mail.gmail.com>
2016-03-18  9:06 ` Outreachy Lars Kurth

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=443f0143-aec1-2559-a2c2-73b245632948@broadcom.com \
    --to=scott.branden@broadcom.com \
    --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=julia.lawall@lip6.fr \
    --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=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: link
Be 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.