linux-kernel - Re: [PATCH] docs/sp_SP: Add memory-barriers.txt Spanish translation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87fsec9foh.fsf@meer.lwn.net>
Date:   Mon, 21 Nov 2022 14:10:54 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Carlos Bilbao <carlos.bilbao@....com>
Cc:     linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        bilbao@...edu, sos-linux-ext-patches@...lman-svr.amd.com,
        Carlos Bilbao <carlos.bilbao@....com>
Subject: Re: [PATCH] docs/sp_SP: Add memory-barriers.txt Spanish translation

Carlos Bilbao <carlos.bilbao@....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@....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