From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
bilbao@vt.edu, sos-linux-ext-patches@mailman-svr.amd.com,
Carlos Bilbao <carlos.bilbao@amd.com>
Subject: Re: [PATCH] docs/sp_SP: Add memory-barriers.txt Spanish translation
Date: Mon, 21 Nov 2022 14:10:54 -0700 [thread overview]
Message-ID: <87fsec9foh.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221111174739.2471900-1-carlos.bilbao@amd.com>
Carlos Bilbao <carlos.bilbao@amd.com> writes:
> Translate the following documents into Spanish:
>
> - memory-barriers.txt
>
> Also include it on index of Spanish translations, following the same
> approach used by the Korean translation, as a note at the end of the index.
>
> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
> ---
> Documentation/translations/sp_SP/index.rst | 4 +
> .../translations/sp_SP/memory-barriers.txt | 3134 +++++++++++++++++
> 2 files changed, 3138 insertions(+)
> create mode 100644 Documentation/translations/sp_SP/memory-barriers.txt
>
> diff --git a/Documentation/translations/sp_SP/index.rst b/Documentation/translations/sp_SP/index.rst
> index e20dd6e875e7..61dace3df9a6 100644
> --- a/Documentation/translations/sp_SP/index.rst
> +++ b/Documentation/translations/sp_SP/index.rst
> @@ -79,3 +79,7 @@ Traducciones al español
>
> howto
> submitting-patches
> +
> +.. include:: ./memory-barriers.txt
> + :literal:
That's an awfully big "note" to add at the end of the index file; I
don't really think that's the best experience for our readers. Can this
be done using the wrapper documents like for English in current
docs-next?
Thanks,
jon
next prev parent reply other threads:[~2022-11-21 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 17:47 [PATCH] docs/sp_SP: Add memory-barriers.txt Spanish translation Carlos Bilbao
2022-11-21 21:10 ` Jonathan Corbet [this message]
2022-11-28 14:53 ` Carlos Bilbao
2022-11-28 15:23 ` [PATCH v2] " Carlos Bilbao
2022-12-03 11:16 ` Jonathan Corbet
2022-12-03 23:11 ` Carlos Bilbao
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=87fsec9foh.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sos-linux-ext-patches@mailman-svr.amd.com \
/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).