From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alessia Mantegazza <amantegazza@vaga.pv.it>
Subject: Re: doc:it_IT: kernel-hacking translation
Date: Sat, 07 Jul 2018 16:38:01 +0200 [thread overview]
Message-ID: <2354575.ij7tX15MBX@harkonnen> (raw)
In-Reply-To: <20180706220517.28623-1-federico.vaga@vaga.pv.it>
On Saturday, July 7, 2018 12:05:15 AM CEST Federico Vaga wrote:
> Ciao Jon,
>
> This small set of patches introduces the kernel-hacking translation in
> Italian and fix the locking.rst internal links. I do not know if this is
> a problem with **my** Sphinx environment but these links were not
> working.
And I forget to say that I changed the header part (translation
information). The idea is that metadata field are less invasive, cleaner,
than notes when rendered in HTML. I think this (metadata fields) is better.
If you agree I will change what I did in doc-guide.
--
Federico Vaga
http://www.federicovaga.it/
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alessia Mantegazza <amantegazza@vaga.pv.it>
Subject: Re: doc:it_IT: kernel-hacking translation
Date: Sat, 07 Jul 2018 16:38:01 +0200 [thread overview]
Message-ID: <2354575.ij7tX15MBX@harkonnen> (raw)
In-Reply-To: <20180706220517.28623-1-federico.vaga@vaga.pv.it>
On Saturday, July 7, 2018 12:05:15 AM CEST Federico Vaga wrote:
> Ciao Jon,
>
> This small set of patches introduces the kernel-hacking translation in
> Italian and fix the locking.rst internal links. I do not know if this is
> a problem with **my** Sphinx environment but these links were not
> working.
And I forget to say that I changed the header part (translation
information). The idea is that metadata field are less invasive, cleaner,
than notes when rendered in HTML. I think this (metadata fields) is better.
If you agree I will change what I did in doc-guide.
--
Federico Vaga
http://www.federicovaga.it/
next prev parent reply other threads:[~2018-07-07 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 22:05 doc:it_IT: kernel-hacking translation Federico Vaga
2018-07-06 22:05 ` Federico Vaga
2018-07-06 22:05 ` [PATCH 1/2] doc:hacking: add labels Federico Vaga
2018-07-06 22:05 ` Federico Vaga
2018-07-26 22:20 ` Jonathan Corbet
2018-07-26 22:20 ` Jonathan Corbet
2018-07-06 22:05 ` [PATCH 2/2] doc:it_IT: translation for kernel-hacking Federico Vaga
2018-07-26 22:23 ` Jonathan Corbet
2018-07-26 22:23 ` Jonathan Corbet
2018-07-27 7:46 ` Federico Vaga
2018-07-27 7:46 ` Federico Vaga
2018-07-27 21:34 ` Jonathan Corbet
2018-07-27 21:34 ` Jonathan Corbet
2018-07-07 14:38 ` Federico Vaga [this message]
2018-07-07 14:38 ` doc:it_IT: kernel-hacking translation 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=2354575.ij7tX15MBX@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.