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,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Subject: Re: [PATCH] doc:it_IT: fix file references
Date: Fri, 7 Jun 2019 11:36:37 -0600 [thread overview]
Message-ID: <20190607113637.6619e846@lwn.net> (raw)
In-Reply-To: <20190530201455.12412-1-federico.vaga@vaga.pv.it>
On Thu, 30 May 2019 22:14:54 +0200
Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> Fix italian translation file references based on
> `scripts/documentation-file-ref-check` output.
>
> Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
Applied, thanks.
jon
prev parent reply other threads:[~2019-06-07 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 20:14 [PATCH] doc:it_IT: fix file references Federico Vaga
2019-05-30 20:14 ` [PATCH] doc:it_IT: documentation alignment Federico Vaga
2019-06-07 17:37 ` Jonathan Corbet
2019-06-04 13:52 ` [PATCH] doc:it_IT: fix file references Mauro Carvalho Chehab
2019-06-07 17:36 ` 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=20190607113637.6619e846@lwn.net \
--to=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@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).