mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bilbao, Carlos" <carlos.bilbao@amd.com>
To: Jonathan Corbet <corbet@lwn.net>, Avadhut Naik <avadhut.naik@amd.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	avadnaik@amd.com
Subject: Re: [PATCH 0/4] Translate development-process into Spanish
Date: Tue, 2 Apr 2024 11:21:36 -0500	[thread overview]
Message-ID: <70e42f58-b3a9-4df2-913f-2f7b605b127c@amd.com> (raw)
In-Reply-To: <874jcjwyb0.fsf@meer.lwn.net>

On 4/2/2024 10:59 AM, Jonathan Corbet wrote:
> Avadhut Naik <avadhut.naik@amd.com> writes:
> 
>> This patch set translates development-process and two of its associated
>> files into Spanish.
>>
>> The first patch updates the Spanish version of process/submitting-patches
>> with the changes recently introduced into its original English version.
>>
>> The second patch translates the process/development-process into
>> Spanish.
>>
>> The third patch translates the process/1.Intro file into Spanish
>>
>> The fourth patch translates process/2.Process file into Spanish.
>>
>> NOTE:
>> In order to avoid broken links in process/1.Intro, empty files have been
>> created for the documents, associated with development-process, that have
>> not been translated yet. Similar approach was taken for Italian
>> translations some time back.
>>
>> Link: https://lore.kernel.org/lkml/20181108232417.14982-1-federico.vaga@vaga.pv.it/
>>
>> Translations for these documents will be submitted within the coming
>> months.
>>
>> Avadhut Naik (4):
>>   docs/sp_SP: Update process/submitting-patches
>>   docs/sp_SP: Add translation of process/development-process.rst
>>   docs/sp_SP: Add translation of process/1.Intro.rst
>>   docs/sp_SP: Add translation of process/2.Process.rst
>>
>>  .../translations/sp_SP/process/1.Intro.rst    | 302 ++++++++++
>>  .../translations/sp_SP/process/2.Process.rst  | 542 ++++++++++++++++++
>>  .../sp_SP/process/3.Early-stage.rst           |  11 +
>>  .../translations/sp_SP/process/4.Coding.rst   |  11 +
>>  .../translations/sp_SP/process/5.Posting.rst  |  11 +
>>  .../sp_SP/process/6.Followthrough.rst         |  11 +
>>  .../sp_SP/process/7.AdvancedTopics.rst        |  11 +
>>  .../sp_SP/process/8.Conclusion.rst            |  11 +
>>  .../sp_SP/process/development-process.rst     |  27 +
>>  .../translations/sp_SP/process/index.rst      |   1 +
>>  .../sp_SP/process/submitting-patches.rst      |  28 +
>>  11 files changed, 966 insertions(+)
> 
> Applied, thanks.

Thank you, Jon!

> 
> jon

Best regards,
Carlos

      reply	other threads:[~2024-04-02 16:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 22:18 Avadhut Naik
2024-03-05 22:18 ` [PATCH 1/4] docs/sp_SP: Update process/submitting-patches Avadhut Naik
2024-03-05 22:18 ` [PATCH 2/4] docs/sp_SP: Add translation of process/development-process.rst Avadhut Naik
2024-03-05 22:18 ` [PATCH 3/4] docs/sp_SP: Add translation of process/1.Intro.rst Avadhut Naik
2024-03-05 22:18 ` [PATCH 4/4] docs/sp_SP: Add translation of process/2.Process.rst Avadhut Naik
2024-04-02 15:59 ` [PATCH 0/4] Translate development-process into Spanish Jonathan Corbet
2024-04-02 16:21   ` Bilbao, Carlos [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=70e42f58-b3a9-4df2-913f-2f7b605b127c@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=avadhut.naik@amd.com \
    --cc=avadnaik@amd.com \
    --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

all inboxes | Powered by JetHome®