All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: outreachy@lists.linux.dev
Subject: [KERNEL NEBIES ACCESS] Sumitra Sharma
Date: Fri, 17 Mar 2023 10:50:07 -0700	[thread overview]
Message-ID: <20230317175007.GA3275@sumitra.com> (raw)

Hi Alison,

The outreachyfirstpatch document directly links the ".rst" files at many places under different sections. And as Fabio says that .rst files are source files and are only meant to be used for making changes and not to consult. Therefore,  I would like to propose the idea of changing the
links of the .rst source files to their respective .html/.pdf files.

The specific changes are:

1. approved email client:

https://elixir.bootlin.com/linux/latest/source/Documentation/process/email-clients.rst
--------------------------------------------------------------
https://www.kernel.org/doc/html/latest/process/email-clients.html


2. coding style:

https://elixir.bootlin.com/linux/latest/source/Documentation/process/coding-style.rst
--------------------------------------------------------------
https://www.kernel.org/doc/html/latest/process/coding-style.html


3. In https://kernelnewbies.org/PatchPhilosophy under the section "Further Reading":

https://elixir.bootlin.com/linux/latest/source/Documentation/process/coding-style.rst
-----------------------------------------------------------------
https://www.kernel.org/doc/html/latest/process/coding-style.html


https://elixir.bootlin.com/linux/latest/source/Documentation/process/submitting-patches.rst
-----------------------------------------------------------------
https://www.kernel.org/doc/html/latest/process/submitting-patches.html


https://elixir.bootlin.com/linux/latest/source/Documentation/process/submit-checklist.rst
-----------------------------------------------------------------
https://www.kernel.org/doc/html/latest/process/submit-checklist.html


Kindly provide me the write mode access and guidance to the further steps to do the same.

Regards,

Sumitra

             reply	other threads:[~2023-03-17 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 17:50 Sumitra Sharma [this message]
2023-03-18  1:14 ` [KERNEL NEBIES ACCESS] Sumitra Sharma Alison Schofield
2023-03-18  6:30   ` Sumitra Sharma
2023-03-18 20:02     ` Alison Schofield

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=20230317175007.GA3275@sumitra.com \
    --to=sumitraartsy@gmail.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.