From: Alison Schofield <alison.schofield@intel.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: patch recipients
Date: Tue, 18 Oct 2022 08:55:28 -0700 [thread overview]
Message-ID: <Y07McBJ9aTHiI87/@aschofie-mobl2> (raw)
In-Reply-To: <Y05AFCN5w/Y2+yeb@debian-BULLSEYE-live-builder-AMD64>
On Tue, Oct 18, 2022 at 11:26:36AM +0530, Deepak R Varma wrote:
> On Mon, Oct 17, 2022 at 10:06:05PM -0700, Alison Schofield wrote:
> > Hi Deepak,
>
> Hello Alison,
>
> >
> > I notice that you started CC'ing mentors directly on your patches.
> That is correct. Actually there is a section "Send your patch to your mentors"
> on the following link. Hence I did that.
>
> https://kernelnewbies.org/Outreachyfirstpatch?action=show&redirect=OPWfirstpatch#kernel-setup-done
Thanks for pointing it out. The content of that section is correct,
but the title of it is wrong. Perhaps a better header would simply
be 'Send your patch' and the detail in the body of that section is
correct.
See my recent email to the list about how to update the First Patch
Tutorial.
>
> >
> > I want to redirect you to the directions in the First Patch Tutorial
> > and the Welcome Announcement on the mailing list. Both talk about patch
> > recipients.
> Sure. I will follow the instructions from here.
>
> >
> > Given that you've started it, you cannot drop them from the current
> > set, because we never trim the recipient list once a set is in flight.
> > Sometimes we grow it.
> That must have been a mistake. I tried to copy them on all my patches. I will
> check which one I missed and ensure I am not missing any recipients going
> forward.
>
> >
> > Also, I'm guessing there is a chance that the mentors privately told
> > you to 'CC them. NAK! That should not be done. Mentors should be
> > subscribed to this list. Let's keep the patch recipient list clean.
> NO, they have not. It was my own assumption based on how I understood the link
> mentioned above. The mentors have not communicated to me anything so far.
When the cleanup patch requirement is complete, then the contact
with the mentors about small tasks for projects begins.
Thanks for your help making the tutorial clearer,
Alison
>
> Thank you,
> ./drv
>
> >
> > Thanks,
> > Alison
>
>
prev parent reply other threads:[~2022-10-18 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 5:06 patch recipients Alison Schofield
2022-10-18 5:56 ` Deepak R Varma
2022-10-18 15:55 ` Alison Schofield [this message]
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=Y07McBJ9aTHiI87/@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=drv@mailo.com \
--cc=outreachy@lists.linux.dev \
/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.