From: Deepak R Varma <drv@mailo.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: [Outreachy Info] How to update the First Patch Tutorial
Date: Sat, 5 Nov 2022 11:48:25 +0530 [thread overview]
Message-ID: <Y2YAMRWzu1CRGe7a@qemulion> (raw)
In-Reply-To: <Y07K+awYX+9wLq9q@aschofie-mobl2>
On Tue, Oct 18, 2022 at 08:49:13AM -0700, Alison Schofield wrote:
>
> We encourage updates to the First Patch Tutorial.
>
> If you update the doc, please post a message to the Outreachy
> mailing list showing the update you made. If you want your
> potential update reviewed first, ask on this list too.
>
> I am a 'watcher' of the page, so I will be notified and
> review the edits to the tutorial automatically.
>
> The directions for contributing to the First Patch Tutorial,
> is a bit buried in the wiki, so I'll point it out here:
>
> See section: Tips for Applying to be an Outreachy Kernel intern
> "Bonus points if you make a kernelnewbies account and correct or add
> knowledge to this wiki. To edit the wiki, create an account, and then
> send an email to the outreachy@lists.linux.dev with the subject
> "[KERNEL NEWBIES ACCESS] username", where username is your kernel
> newbies username."
>
> One update I would suggest is creating a sub-section about updating
> the wiki - to make it more obvious.
Hello Alison,
Can I add this "Updating Newbies Wiki" suggested section to the wiki pagexi
now? If yes, who should I share my updates with?
Thank you,
./drv
>
> Thanks,
> Alison
>
next prev parent reply other threads:[~2022-11-05 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:49 [Outreachy Info] How to update the First Patch Tutorial Alison Schofield
2022-11-05 6:18 ` Deepak R Varma [this message]
2022-11-09 1:05 ` Alison Schofield
2022-11-09 4:05 ` Deepak R Varma
2022-11-09 8:11 ` Deepak R Varma
2022-11-13 5:33 ` Deepak R Varma
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=Y2YAMRWzu1CRGe7a@qemulion \
--to=drv@mailo.com \
--cc=alison.schofield@intel.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.