public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: corbet@lwn.net, avadhut.naik@amd.com, bilbao@vt.edu
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] docs/sp_SP: Translate development process into Spanish
Date: Fri, 29 Nov 2024 09:58:40 -0600	[thread overview]
Message-ID: <20241129155851.1023884-1-carlos.bilbao.osdev@gmail.com> (raw)

From: Avadhut Naik <avadhut.naik@amd.com>

This patchset translates the remaining documents of development-process
into Spanish.

The first patch translates process/3.Early-stage into Spanish.

The second patch translates process/4.Coding into Spanish.

The third patch translates process/5.Posting into Spanish.

The fourth patch translates process/6.Followthrough into Spanish.

The fifth patch translates process/7.AdvancedTopics into Spanish.

The sixth patch translates process/8.Conclusion into Spanish.

The seventh patch moves development-process to the top of the index for
translated docs to match the layout in the main Documentation index.

Avadhut Naik (3):
  docs/sp_SP: Add translation of process/5.Posting.rst
  docs/sp_SP: Add translation of process/7.AdvancedTopics.rst
  docs/sp_SP: Add translation of process/8.Conclusion.rst

Carlos Bilbao (4):
  docs/sp_SP: Add translation of process/3.Early-stage.rst
  docs/sp_SP: Add translation of process/4.Coding.rst
  docs/sp_SP: Add translation of process/6.Followthrough.rst
  docs/sp_SP: Move development-process to top of index

 .../sp_SP/process/3.Early-stage.rst           | 234 ++++++++-
 .../translations/sp_SP/process/4.Coding.rst   | 463 +++++++++++++++++-
 .../translations/sp_SP/process/5.Posting.rst  | 388 ++++++++++++++-
 .../sp_SP/process/6.Followthrough.rst         | 223 ++++++++-
 .../sp_SP/process/7.AdvancedTopics.rst        | 207 +++++++-
 .../sp_SP/process/8.Conclusion.rst            |  75 ++-
 .../sp_SP/process/development-process.rst     |  21 +-
 .../translations/sp_SP/process/index.rst      |   2 +-
 8 files changed, 1590 insertions(+), 23 deletions(-)


base-commit: ed9a4ad6e5bd3a443e81446476718abebee47e82
-- 
2.43.0


             reply	other threads:[~2024-11-29 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 15:58 Carlos Bilbao [this message]
2024-11-29 15:58 ` [PATCH 1/7] docs/sp_SP: Add translation of process/3.Early-stage.rst Carlos Bilbao
2024-11-29 15:58 ` [PATCH 2/7] docs/sp_SP: Add translation of process/4.Coding.rst Carlos Bilbao
2024-11-29 15:58 ` [PATCH 3/7] docs/sp_SP: Add translation of process/5.Posting.rst Carlos Bilbao
2024-11-29 15:58 ` [PATCH 4/7] docs/sp_SP: Add translation of process/6.Followthrough.rst Carlos Bilbao
2024-11-29 15:58 ` [PATCH 5/7] docs/sp_SP: Add translation of process/7.AdvancedTopics.rst Carlos Bilbao
2024-11-29 15:58 ` [PATCH 6/7] docs/sp_SP: Add translation of process/8.Conclusion.rst Carlos Bilbao
2024-11-29 15:58 ` [PATCH 7/7] docs/sp_SP: Move development-process to top of index Carlos Bilbao
2024-12-06 16:27 ` [PATCH 0/7] docs/sp_SP: Translate development process into Spanish Jonathan Corbet

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=20241129155851.1023884-1-carlos.bilbao.osdev@gmail.com \
    --to=carlos.bilbao.osdev@gmail.com \
    --cc=avadhut.naik@amd.com \
    --cc=bilbao@vt.edu \
    --cc=corbet@lwn.net \
    --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