linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Subject: Re: Why no section for "Kernel/Linux Documentation" here : https://patchwork.kernel.org/
Date: Mon, 30 Sep 2019 11:13:21 -0600	[thread overview]
Message-ID: <20190930111321.30b90efd@lwn.net> (raw)
In-Reply-To: <20190930155826.GC27688@Slackware>

On Mon, 30 Sep 2019 21:28:26 +0530
Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:

>  Why that page missing a section "Kernel Documentation" ?? OR am I
>  missing the title there....not sure...there must be some reason.

Many kernel subsystems do not use patchwork; documentation has always been
one of them.  Perhaps that should change someday; let's see how the
workflow discussions go.

jon

      reply	other threads:[~2019-09-30 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 15:58 Why no section for "Kernel/Linux Documentation" here : https://patchwork.kernel.org/ Bhaskar Chowdhury
2019-09-30 17:13 ` Jonathan Corbet [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=20190930111321.30b90efd@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=unixbhaskar@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).