From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
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 09:46:47 +0200 [thread overview]
Message-ID: <1944849.qmSSJrysef@pcbe13614> (raw)
In-Reply-To: <20180726162330.786826cf@lwn.net>
I know, but I believe they are still good documents if read with a bit of
pragmatism: many concepts there are evergreen. Then, it clearly says
"unreliable" ;P
Your wonder, make me wonder. 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)? Clearly here it says that it has been
written for Linux 2.6, but most documents do not say anything about the last
significant review/update. This let people think that documentation and code
are always in sync. How this is handled? Just by enforcing people to update
the documentation when they change, for example, an interface that has been
documented?
On Friday, July 27, 2018 12:23:30 AM CEST Jonathan Corbet wrote:
> On Sat, 7 Jul 2018 00:05:17 +0200
>
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> > This patch includes the kernel-hacking translation in Italian (both
> > hacking.rst and locking.rst).
> >
> > It adds also the anchors for the english kernel-hacking documents.
>
> Applied, thanks. Though I do have to wonder a bit, since these documents
> are ancient and haven't seen a lot of maintenance in recent times...
>
> jon
--
Federico Vaga
http://www.federicovaga.it/
--
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
next prev parent reply other threads:[~2018-07-27 7:46 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 [this message]
2018-07-27 21:34 ` Jonathan Corbet
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=1944849.qmSSJrysef@pcbe13614 \
--to=federico.vaga@vaga.pv.it \
--cc=amantegazza@vaga.pv.it \
--cc=corbet@lwn.net \
--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).