From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alessia Mantegazza <amantegazza@vaga.pv.it>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] doc:it_IT: update italian documentation
Date: Fri, 9 Nov 2018 00:24:14 +0100 [thread overview]
Message-ID: <20181108232417.14982-1-federico.vaga@vaga.pv.it> (raw)
In this small patch set there is the V3 of
"doc:it_IT: add some process/* translations" in which I fixed
the recent conflicts in docs-next.
I took the occasion to add other two simple patches that fix:
- a missing translation in locking.rst
- apply a patch from the official documentation to the italian one
next reply other threads:[~2018-11-08 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 23:24 Federico Vaga [this message]
2018-11-08 23:24 ` [PATCH V3 1/3] doc:it_IT: add some process/* translations Federico Vaga
2018-11-08 23:24 ` [PATCH 2/3] doc:it_IT: fix locking.rst section title Federico Vaga
2018-11-08 23:24 ` [PATCH 3/3] doc:it_IT:doc-guide: fix reference to foobar Federico Vaga
2018-11-20 16:16 ` [PATCH 0/3] doc:it_IT: update italian documentation Jonathan Corbet
2018-11-21 0:24 ` Federico Vaga
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=20181108232417.14982-1-federico.vaga@vaga.pv.it \
--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).