linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org, Martin Kepplinger <martink@posteo.de>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kernel-docs: Move vfs.txt under "Docs at the Linux Kernel tree"
Date: Tue, 2 Apr 2019 09:43:58 -0600	[thread overview]
Message-ID: <20190402094358.38c15809@lwn.net> (raw)
In-Reply-To: <20190331221439.22892-1-j.neuschaefer@gmx.net>

On Mon,  1 Apr 2019 00:14:37 +0200
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:

> It's unnecessary to point to an external mirror of the Documentation
> directory. Also, drop the date field, because in-kernel documentation is
> continually updated.

So I had to ponder on this one a bit...saying "continually updated" is
pretty amusing for a document that leads off with:

		  Last updated on June 24, 2007.

> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> 
> Alternatively, we might drop this entry of the list entirely, because
> Documentation/ is already covered.

In the end, I think this alternative option is the better one.  We don't
want to turn kernel-docs.rst into yet another out-of-date index for the
rest of Documentation/, and the removal of the external URL takes away the
only bit of additional information that this entry offers.

Thanks,

jon

  parent reply	other threads:[~2019-04-02 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-31 22:14 [PATCH] Documentation: kernel-docs: Move vfs.txt under "Docs at the Linux Kernel tree" Jonathan Neuschäfer
2019-04-01  5:19 ` Martin Kepplinger
2019-04-02 15:43 ` Jonathan Corbet [this message]
2019-04-02 19:13   ` Jonathan Neuschäfer

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=20190402094358.38c15809@lwn.net \
    --to=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martink@posteo.de \
    /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).