public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Edwin Toribio <edwin.toribio.j@gmail.com>
Cc: carlos.bilbao@kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, rust-for-linux@vger.kernel.org,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH v2 0/3] docs: sp_SP: Add Rust documentation section
Date: Sun, 8 Mar 2026 11:29:44 -0700	[thread overview]
Message-ID: <f7e1ce48-cc0f-4365-bb6f-1af2635dffd2@gmail.com> (raw)
In-Reply-To: <20260304200715.76360-1-edwin.toribio.j@gmail.com>

Hello Edwin,

On 3/4/26 12:07, Edwin Toribio wrote:
> This series provides the Spanish translation for the Rust documentation
> section in the Linux kernel, including the quick-start guide, general
> information, and coding guidelines.
>
> In this second version, all documents have been unified and updated to
> comply with the feedback provided regarding style and technical accuracy.
>
> Changes in v2:
> - Added new translations: coding-guidelines.rst and index.rst.
> - Standardized the use of "p. ej." abbreviation throughout all files.
> - Fixed the Hacking section truncation in quick-start.rst.
>
> Edwin Toribio (3):
>    docs: sp_SP: Add Spanish translation for Rust quick-start
>    docs: sp_SP: Add Spanish translation for Rust general information
>    docs: sp_SP: Add Spanish translation for Rust coding guidelines
>
>   .../sp_SP/rust/coding-guidelines.rst          | 543 ++++++++++++++++++
>   .../sp_SP/rust/general-information.rst        | 178 ++++++
>   .../translations/sp_SP/rust/index.rst         |  45 ++
>   .../translations/sp_SP/rust/quick-start.rst   | 384 +++++++++++++
>   4 files changed, 1150 insertions(+)
>   create mode 100644 Documentation/translations/sp_SP/rust/coding-guidelines.rst
>   create mode 100644 Documentation/translations/sp_SP/rust/general-information.rst
>   create mode 100644 Documentation/translations/sp_SP/rust/index.rst
>   create mode 100644 Documentation/translations/sp_SP/rust/quick-start.rst

Thanks, Edwin, this is much better! We're close, but not quite there yet.
We'll need a v3 for a couple of reasons.

Thanks,

Carlos


      parent reply	other threads:[~2026-03-08 18:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 20:07 [PATCH v2 0/3] docs: sp_SP: Add Rust documentation section Edwin Toribio
2026-03-04 20:07 ` [PATCH v2 1/3] docs: sp_SP: Add Spanish translation for Rust quick-start Edwin Toribio
2026-03-08 18:29   ` Carlos Bilbao
2026-03-08 18:38   ` Carlos Bilbao
2026-03-04 20:07 ` [PATCH v2 2/3] docs: sp_SP: Add Spanish translation for Rust general information Edwin Toribio
2026-03-08 18:31   ` Carlos Bilbao
2026-03-04 20:07 ` [PATCH v2 3/3] docs: sp_SP: Add Spanish translation for Rust coding guidelines Edwin Toribio
2026-03-08 18:40   ` Carlos Bilbao
2026-03-08 19:16     ` Miguel Ojeda
2026-03-10  3:33       ` Carlos Bilbao
2026-03-10 20:14         ` Miguel Ojeda
2026-03-10 23:57           ` Carlos Bilbao
2026-03-11  6:11             ` Miguel Ojeda
2026-03-13  2:12               ` Carlos Bilbao
2026-03-08 18:29 ` Carlos Bilbao [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=f7e1ce48-cc0f-4365-bb6f-1af2635dffd2@gmail.com \
    --to=carlos.bilbao.osdev@gmail.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=edwin.toribio.j@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@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