From: Federico Vaga <federico.vaga@cern.ch>
To: Jonathan Corbet <corbet@lwn.net>, <amantegazza@vaga.pv.it>
Cc: <linux-doc@vger.kernel.org>
Subject: Italian translations and broken links
Date: Fri, 24 Aug 2018 13:51:18 +0200 [thread overview]
Message-ID: <3898461.lmkq0IsokZ@pcbe13614> (raw)
Hi Jon,
just one question about how do you prefer us to proceed. We are translating
the process directory.
My idea was to complete it and then push it. This because the documents in
here have links to other documents in the same directory. In order to cleanly
build it I wanted to translate the full directory and then propose a patch.
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)?
Thanks :)
next reply other threads:[~2018-08-24 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 11:51 Federico Vaga [this message]
2018-08-24 11:52 ` Italian translations and broken links Federico Vaga
2018-08-24 13:21 ` 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=3898461.lmkq0IsokZ@pcbe13614 \
--to=federico.vaga@cern.ch \
--cc=amantegazza@vaga.pv.it \
--cc=corbet@lwn.net \
--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).