From: Jonathan Corbet <corbet@lwn.net>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alessia Mantegazza <amantegazza@vaga.pv.it>
Subject: Re: [PATCH 2/2] doc:it_IT: translation for kernel-hacking
Date: Fri, 27 Jul 2018 15:34:24 -0600 [thread overview]
Message-ID: <20180727153424.7bba09ce@lwn.net> (raw)
In-Reply-To: <1944849.qmSSJrysef@pcbe13614>
On Fri, 27 Jul 2018 09:46:47 +0200
Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> Generally speaking, how readers can understand
> how old is a document or if it still correct (in the sense that the document
> and the correspondent code are in sync)?
We don't have a good answer to that, really. Some of our docs are
up-to-the-second current, and others still talk about how to find out
which vacuum tube has gone bad in your system. It's a trap for our
readers, unfortunately. My plan has been to try to bring some more order
to Documentation/ first, hopefully cleaning things up a bit on the way.
> How this is handled? Just by enforcing people to update
> the documentation when they change, for example, an interface that has been
> documented?
magari ... talk of such enforcement is a recurring thing, but nobody has
the will to actually do that.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-07-27 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 22:05 doc:it_IT: kernel-hacking translation Federico Vaga
2018-07-06 22:05 ` [PATCH 1/2] doc:hacking: add labels Federico Vaga
2018-07-26 22:20 ` Jonathan Corbet
2018-07-07 14:38 ` doc:it_IT: kernel-hacking translation Federico Vaga
[not found] ` <20180706220517.28623-3-federico.vaga@vaga.pv.it>
2018-07-26 22:23 ` [PATCH 2/2] doc:it_IT: translation for kernel-hacking Jonathan Corbet
2018-07-27 7:46 ` Federico Vaga
2018-07-27 21:34 ` 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=20180727153424.7bba09ce@lwn.net \
--to=corbet@lwn.net \
--cc=amantegazza@vaga.pv.it \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).