linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	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 21:13:17 +0200	[thread overview]
Message-ID: <20190402191317.GG2095@latitude> (raw)
In-Reply-To: <20190402094358.38c15809@lwn.net>

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On Tue, Apr 02, 2019 at 09:43:58AM -0600, Jonathan Corbet wrote:
> 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.

Ok, I should have been more explicit with what I meant and written "(in
principle) continually update"; compared to journal articles or sections
of a specific edition of a book, that's what files in Git are.

However, looking at the Git history for vfs.txt, it has indeed been
updated multiple times per year, and not just with typo fixes, so I
think this line should simply be removed to avoid further confusion.

> 
> > 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.

Good points, I'll do that for v2.


Jonathan Neuschäfer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-04-02 19:13 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
2019-04-02 19:13   ` Jonathan Neuschäfer [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=20190402191317.GG2095@latitude \
    --to=j.neuschaefer@gmx.net \
    --cc=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --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).