From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Cc: bilbao@vt.edu, jembid@ucm.es, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Subject: Re: [PATCH] docs/sp_SP: Add translation of process/maintainer-kvm-x86.rst
Date: Wed, 03 Jul 2024 16:35:28 -0600 [thread overview]
Message-ID: <87bk3et87j.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240626221942.2780668-1-carlos.bilbao.osdev@gmail.com>
Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:
> Translate Documentation/process/maintainer-kvm-x86.rst into Spanish.
>
> Co-developed-by: Juan Embid <jembid@ucm.es>
> Signed-off-by: Juan Embid <jembid@ucm.es>
> Signed-off-by: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
> ---
> .../translations/sp_SP/process/index.rst | 1 +
> .../sp_SP/process/maintainer-kvm-x86.rst | 466 ++++++++++++++++++
> 2 files changed, 467 insertions(+)
> create mode 100644 Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst
I've applied this, but it generated two warnings. One on application:
.git/rebase-apply/patch:487: new blank line at EOF.
and one during the build:
Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst:3: WARNING: undefined label: 'documentation/process/maintainer-kvm-x86.rst'
I fixed both of these (see patch below) but would really rather not have
to clean up things like this.
Thanks,
jon
diff --git a/Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst b/Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst
index 127238f44ea9..053b6a06db01 100644
--- a/Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst
+++ b/Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst
@@ -1,6 +1,6 @@
.. include:: ../disclaimer-sp.rst
-:Original: :ref:`Documentation/process/maintainer-kvm-x86.rst`
+:Original: Documentation/process/maintainer-kvm-x86.rst
:Translator: Juan Embid <jembid@ucm.es>
KVM x86
@@ -463,4 +463,3 @@ host (kernel o espacio de usuario), o que pueden ser explotados por una VM
anidada a *su* host (L2 atacando a L1), son de particular interés para KVM.
Por favor, siga el protocolo para :ref:`securitybugs` si sospecha que un
fallo puede provocar una filtración de datos, etc.
-
prev parent reply other threads:[~2024-07-03 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 22:19 Carlos Bilbao
2024-07-03 22:35 ` Jonathan Corbet [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=87bk3et87j.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=jembid@ucm.es \
--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
all inboxes | Powered by JetHome®