linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <si.yanteng@linux.dev>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: alexs@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH] docs/zh_CN: Add how-to of Chinese translation
Date: Tue, 4 Mar 2025 15:06:35 +0800	[thread overview]
Message-ID: <9ebb6a57-8683-450f-9126-4a68bd2bfe3d@linux.dev> (raw)
In-Reply-To: <CAD-N9QUgstCA+nGb=b6DBe+C2eU180YKn=U7x1WKS-RqyJVaxg@mail.gmail.com>


在 2/27/25 8:18 PM, Dongliang Mu 写道:
> On Thu, Feb 27, 2025 at 6:36 PM Yanteng Si <si.yanteng@linux.dev> wrote:
>> Many new faces keep appearing on the mailing list from time to
>> time, and there may be many potential developers who want to
>> participate in the Chinese translation but don't know how to
>> get started. As more and more documents are translated, it is
>> becoming increasingly important to improve the maintainability
>> of Chinese documents. We have a lot of conventions, but currently
>> these conventions are still being passed on orally. At the same
>> time, during the review process, especially for the first few
>> patches submitted by newbies, we have made too many repetitive
>> comments. In order to address the above issues, I have drafted
>> this guide, and there is still a lot that needs to be improved.
>>
> Quick comments about "b4 am", the warning needs to be addressed.
>
> -------------------------------------------------------------------------------------------------------------------------------------
>   $ b4 am 20250227103602.321198-1-si.yanteng@linux.dev
> Grabbing thread from
> lore.kernel.org/all/20250227103602.321198-1-si.yanteng@linux.dev/t.mbox.gz
> Analyzing 1 messages in the thread
> Looking for additional code-review trailers on lore.kernel.org
> Checking attestation on all messages, may take a moment...
> ---
>    ✓ [PATCH RFC] docs/zh_CN: Add how-to of Chinese translation
>    ---
>    ✓ Signed: DKIM/linux.dev
> ---
> Total patches: 1
> ---
>   Link: https://lore.kernel.org/r/20250227103602.321198-1-si.yanteng@linux.dev
>   Base: applies clean to current tree
>         git checkout -b 20250227_si_yanteng_linux_dev HEAD
>         git am ./20250227_si_yanteng_docs_zh_cn_add_how_to_of_chinese_translation.mbx
>
> $ git checkout -b 20250227_si_yanteng_linux_dev HEAD
> Switched to a new branch '20250227_si_yanteng_linux_dev'
>
> $ git am ./20250227_si_yanteng_docs_zh_cn_add_how_to_of_chinese_translation.mbx
> Applying: docs/zh_CN: Add how-to of Chinese translation
> .git/rebase-apply/patch:454: new blank line at EOF.
> +
> warning: 1 line adds whitespace errors.

Will fix.


Thanks,

Yanteng


  reply	other threads:[~2025-03-04  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 10:36 [RFC PATCH] docs/zh_CN: Add how-to of Chinese translation Yanteng Si
2025-02-27 12:18 ` Dongliang Mu
2025-03-04  7:06   ` Yanteng Si [this message]
2025-02-27 12:51 ` Dongliang Mu
2025-03-04  7:30   ` Yanteng Si
2025-03-05  2:09     ` Dongliang Mu
2025-03-05  2:14       ` Dongliang Mu
2025-03-11  7:51       ` Yanteng Si
2025-03-12  1:35         ` Alex Shi
2025-02-28  3:24 ` Alex Shi
2025-03-04 10:02   ` Yanteng Si
2025-03-11  7:35     ` Yanteng Si

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=9ebb6a57-8683-450f-9126-4a68bd2bfe3d@linux.dev \
    --to=si.yanteng@linux.dev \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=mudongliangabcd@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;
as well as URLs for NNTP newsgroup(s).