linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Re: [PATCH V2] doc:it_IT: add some process/* translations
Date: Thu, 08 Nov 2018 23:49:25 +0100	[thread overview]
Message-ID: <8336640.hExbF9JPVd@harkonnen> (raw)
In-Reply-To: <20181107152258.48267a2a@lwn.net>

On Wednesday, November 7, 2018 11:22:58 PM CET Jonathan Corbet wrote:
> On Fri,  5 Oct 2018 20:51:57 +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
> 
> So I'm (finally) ready to apply this, but it has conflicts against current
> docs-next.  Could I ask you, please, to send me a respin?

Ok, I'm going to prepare it. I will send also a couple of minor fixes that I 
ported to the Italian translation from the main documents.




      reply	other threads:[~2018-11-08 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181005185157.27819-1-federico.vaga@vaga.pv.it>
2018-10-07 14:42 ` [PATCH V2] doc:it_IT: add some process/* translations Jonathan Corbet
2018-10-10 17:01   ` Federico Vaga
2018-11-07 22:22 ` Jonathan Corbet
2018-11-08 22:49   ` Federico Vaga [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=8336640.hExbF9JPVd@harkonnen \
    --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).