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,
Alessia Mantegazza <amantegazza@vaga.pv.it>
Subject: Re: [PATCH] doc:it_IT: add some process/* translations
Date: Thu, 20 Sep 2018 14:35:11 -0600 [thread overview]
Message-ID: <20180920143511.26136ddd@lwn.net> (raw)
In-Reply-To: <20180920142957.09000163@lwn.net>
On Thu, 20 Sep 2018 14:29:57 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> On Sun, 9 Sep 2018 18:16:41 +0200
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
>
> > This patch does not translate entirely the subfolder "process/"
> > but only part of it (to begin with).
> >
> > In order to avoid broken links, I included empty documents
> > for those which are not yet translated.
> >
> > In order to be able to refer to all documents in "process/",
> > I added a sphinx label to those which had not one.
> >
> > Translated documents:
> > - howto
> > - 1.Intro
> > - clang-format
> > - coding-style
> > - kernel-driver-statement
> > - magic-number
> > - volatile-considered-harmful
> > - development-process
> >
> > Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
> > Signed-off-by: Alessia Mantegazza <amantegazza@vaga.pv.it>
>
> Applied, thanks.
Actually, I just backed that out, sorry. There's an immediate conflict
with -next over code-of-conflict.rst that is best avoided, and there is
no point in adding a translation of the old code. If you can respin the
patch set without that change, I'll apply it.
Thanks,
jon
next prev parent reply other threads:[~2018-09-20 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 16:16 [PATCH] doc:it_IT: add some process/* translations Federico Vaga
2018-09-20 20:29 ` Jonathan Corbet
2018-09-20 20:35 ` Jonathan Corbet [this message]
2018-10-02 8:43 ` 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=20180920143511.26136ddd@lwn.net \
--to=corbet@lwn.net \
--cc=amantegazza@vaga.pv.it \
--cc=federico.vaga@vaga.pv.it \
--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).