From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Jonathan Corbet <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc: add translation disclaimer
Date: Fri, 15 Mar 2019 11:55:17 +0100 [thread overview]
Message-ID: <2230052.up2SEFjotJ@pcbe13614> (raw)
In-Reply-To: <78830124-9f65-354c-ed16-3f73f5ebe0b3@rasmusvillemoes.dk>
On Friday, March 15, 2019 11:00:57 AM CET Rasmus Villemoes wrote:
> On 14/03/2019 21.45, Federico Vaga wrote:
> > diff --git a/Documentation/translations/index.rst
> > b/Documentation/translations/index.rst index 7f77c52d33aa..d7a38fd28b50
> > 100644
> > --- a/Documentation/translations/index.rst
> > +++ b/Documentation/translations/index.rst
> > @@ -4,6 +4,48 @@
> >
> > Translations
> > ============
> >
> > +.. _translations_disclaimer:
> > +
> > +Disclaimer
> > +----------
> > +
> > +Translation's purpose is to ease reading and understating in languages
> > other
> understanding, hopefully :)
ops, yes :D
>
> > +If you need to communicate with the Linux community but you do not feel
> > +comfortable to write in English, you can ask to the translation's
> > +maintainers for help.
> > +
>
> s/to write/writing/, s/ask to/ask/
ack
> > +Translations
> > +------------
> > +
>
> Do you really mean to add that heading a second time? I know it's on
> another level, but it seems a bit odd.
You are right
>
> Rasmus
--
Federico Vaga
http://www.federicovaga.it/
next prev parent reply other threads:[~2019-03-15 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 20:45 [PATCH] doc: add translation disclaimer Federico Vaga
2019-03-15 5:49 ` Alex Shi
2019-03-15 8:09 ` Federico Vaga
2019-03-15 23:00 ` Federico Vaga
2019-03-15 10:00 ` Rasmus Villemoes
2019-03-15 10:55 ` Federico Vaga [this message]
2019-03-18 17:35 ` Jonathan Corbet
2019-03-19 8:03 ` Federico Vaga
2019-03-19 13:35 ` Jonathan Corbet
2019-03-23 17:37 ` 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=2230052.up2SEFjotJ@pcbe13614 \
--to=federico.vaga@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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.