From: Jonathan Corbet <corbet@lwn.net>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: <amantegazza@vaga.pv.it>, <linux-doc@vger.kernel.org>
Subject: Re: Italian translations and broken links
Date: Fri, 24 Aug 2018 07:21:50 -0600 [thread overview]
Message-ID: <20180824072150.51b890c8@lwn.net> (raw)
In-Reply-To: <3898461.lmkq0IsokZ@pcbe13614>
On Fri, 24 Aug 2018 13:51:18 +0200
Federico Vaga <federico.vaga@cern.ch> wrote:
> Since there are many documents, this take time and perhaps we can already push
> the ones which are ready.
>
> My big dilemma is (which is more general): what about broken references? Do we
> keep broken links which we know they will be correct in the future? Or, do we
> remove all broken links and we add them back only when they work (if we
> remember)?
We want the kernel to be as close to release-ready as it can be at any
time, that includes the docs. So please no broken links. It's a bit
more work to keep things coherent, but it's what we need to do in the
long run.
Thanks,
jon
prev parent reply other threads:[~2018-08-24 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 11:51 Italian translations and broken links Federico Vaga
2018-08-24 11:52 ` Federico Vaga
2018-08-24 13:21 ` 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=20180824072150.51b890c8@lwn.net \
--to=corbet@lwn.net \
--cc=amantegazza@vaga.pv.it \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@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).