mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, sergio.collado@gmail.com
Subject: Re: [PATCH] docs/sp_SP: Add process deprecated translation
Date: Mon, 6 Mar 2023 09:20:33 -0600	[thread overview]
Message-ID: <875b2564-589b-c381-cbf0-f30470d4a5a8@amd.com> (raw)
In-Reply-To: <38cb9f23-a56a-f420-5942-0bfeb620306e@gmail.com>

Hello Akira,

On 3/6/23 09:13, Akira Yokosawa wrote:
> Hi Carlos,
> 
> Minor nits in the Subject and Sob area.
> 
> On Mon, 6 Mar 2023 07:44:20 -0600, Carlos Bilbao wrote:
>> Subject: [PATCH] docs/sp_SP: Add process deprecated translation
> 
> This summary looks ambiguous to me.
> 
> Maybe
> 
>     docs/sp_SP: Add translation of process/deprecated

This summary follows the same format followed in the past. Some examples:

docs/sp_SP: Add process coding-style translation
docs/sp_SP: Add process magic-number translation
docs/sp_SP: Add process programming-language translation
docs/sp_SP: Add process email-clients translation

> 
> ??
> 
>> Translate Documentation/process/deprecated.rst into Spanish.
>>
>> Co-developed-by: Carlos Bilbao <carlos.bilbao@amd.com>
>> Signed-off-by: Sergio Gonzalez <sergio.collado@gmail.com>
>> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
> 
> To me, Co-developed-by: from the author of the patch looks
> strange, because it is obvious the author did some development on
> the patch.
> 

No, we both worked on this patch so Co-developed-by: is the appropriate
tagging. That being said, Sergio translated more than I did, so I put
him as sole Translator in the document itself.

> Which is your intent:
> 
>     Author: Carlos
>     Co-developer: Sergio
> 
> , or
> 
>     Author: Sergio
>     Co-developer: Carlos
> 
> ???
> 
>          Thanks, Akira
> 
>> ---
>>   .../translations/sp_SP/process/deprecated.rst | 381 ++++++++++++++++++
>>   .../translations/sp_SP/process/index.rst      |   1 +
>>   2 files changed, 382 insertions(+)
>>   create mode 100644 Documentation/translations/sp_SP/process/deprecated.rst
> [...]

Thanks,
Carlos

  reply	other threads:[~2023-03-06 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 13:44 Carlos Bilbao
2023-03-06 15:13 ` Akira Yokosawa
2023-03-06 15:20   ` Carlos Bilbao [this message]
2023-03-06 15:30     ` Akira Yokosawa
2023-03-06 15:34       ` Carlos Bilbao
2023-03-06 23:03         ` Akira Yokosawa
2023-03-07 13:41           ` Carlos Bilbao

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=875b2564-589b-c381-cbf0-f30470d4a5a8@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio.collado@gmail.com \
    /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®