All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhangwei <zhangwei@cqsoftware.com.cn>
To: Jonathan Corbet <corbet@lwn.net>, alexs@kernel.org, si.yanteng@linux.dev
Cc: zhaoshuo@cqsoftware.com.cn, zhaoyuehui@cqsoftware.com.cn,
	maoyuxian@cqsoftware.com.cn, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs/zh_CN: Add self-protection index Chinese translation
Date: Wed, 5 Feb 2025 10:50:21 +0800	[thread overview]
Message-ID: <ea95aaf2-87ea-4fcb-b88d-3739205ba5af@cqsoftware.com.cn> (raw)
In-Reply-To: <87y0ylfy2q.fsf@trenco.lwn.net>


在 2025/2/5 0:56, Jonathan Corbet 写道:
> zhangwei <zhangwei@cqsoftware.com.cn> writes:
>
>> 在 2025/1/21 13:12, zhangwei 写道:
>>> Translate .../security/self-protection.rst into Chinese.
>>>
>>> Update the translation through commit b080e52110ea
>>> ("docs: update self-protection __ro_after_init status")
>>>
>>> Signed-off-by: zhangwei <zhangwei@cqsoftware.com.cn>
>>> ---
>> Hi, jon
>> Please apply Zhao Shuo's patchset first, and then apply mine.
>> https://lore.kernel.org/linux-doc/cover.1737603330.git.zhaoshuo@cqsoftware.com.cn/
>> <https://lore.kernel.org/linux-doc/cover.1737603330.git.zhaoshuo@cqsoftware.com.cn/>
>>
> I did that, but yours still fails to apply.  Can you send me a respin
> against docs-next, please?
>
> Thanks,
>
> jon

[root@fedora lwn]# git branch
* docs-next
   master
[root@fedora lwn]# git pull
Already up to date.
[root@fedora lwn]# b4 am 20250121051234.79066-1-zhangwei@cqsoftware.com.cn
Grabbing thread from 
lore.kernel.org/all/20250121051234.79066-1-zhangwei@cqsoftware.com.cn/t.mbox.gz
Analyzing 5 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
   ✓ [PATCH v2] docs/zh_CN: Add self-protection index Chinese translation
     + Reviewed-by: Yanteng Si <si.yanteng@linux.dev> (✓ DKIM/linux.dev)
     + Reviewed-by: Yuxian Mao <maoyuxian@cqsoftware.com.cn> (✓ 
DKIM/cqsoftware.com.cn)
   ---
   ✓ Signed: DKIM/cqsoftware.com.cn
---
Total patches: 1
---
  Link: 
https://lore.kernel.org/r/20250121051234.79066-1-zhangwei@cqsoftware.com.cn
  Base: applies clean to current tree
        git checkout -b v2_20250121_zhangwei_cqsoftware_com_cn HEAD
        git am 
./v2_20250121_zhangwei_docs_zh_cn_add_self_protection_index_chinese_translation.mbx
[root@fedora lwn]# git am 
./v2_20250121_zhangwei_docs_zh_cn_add_self_protection_index_chinese_translation.mbx
Applying: docs/zh_CN: Add self-protection index Chinese translation
[root@fedora lwn]#


I re-pushed it and it was possible to punch in the patch.

How do I modify it

Thanks,
zhangwei

>

  reply	other threads:[~2025-02-05  7:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  5:12 [PATCH v2] docs/zh_CN: Add self-protection index Chinese translation zhangwei
2025-01-22  9:21 ` Yanteng Si
2025-01-23  2:51 ` Yuxian Mao
2025-01-24  9:54 ` zhangwei
2025-02-04 16:56   ` Jonathan Corbet
2025-02-05  2:50     ` zhangwei [this message]
2025-02-05  6:16     ` Yanteng Si
2025-02-05  6:19       ` zhangwei

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=ea95aaf2-87ea-4fcb-b88d-3739205ba5af@cqsoftware.com.cn \
    --to=zhangwei@cqsoftware.com.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=maoyuxian@cqsoftware.com.cn \
    --cc=si.yanteng@linux.dev \
    --cc=zhaoshuo@cqsoftware.com.cn \
    --cc=zhaoyuehui@cqsoftware.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.