From: Wan Jiabing <wanjiabing@vivo.com>
To: Alex Shi <alexs@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kael_w@yeah.net, Wan Jiabing <wanjiabing@vivo.com>
Subject: [PATCH] docs/zh_CN: make reporting-bugs.rst obsolete
Date: Thu, 6 May 2021 16:32:07 +0800 [thread overview]
Message-ID: <20210506083207.15705-1-wanjiabing@vivo.com> (raw)
In commit d2ce285378b09 ("docs: make reporting-issues.rst official
and delete reporting-bugs.rst"),reporting-bugs.rst was deleted and
replaced by reporting-issues.rst.
In commit da514157c4f06 ("docs: make reporting-bugs.rst obsolete"),
it made reporting-bugs.rst obsolete in docs.
Fix it in docs/zh_CN to make reporting-bugs.rst obsolete.
Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
---
Documentation/translations/zh_CN/SecurityBugs | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/translations/zh_CN/SecurityBugs b/Documentation/translations/zh_CN/SecurityBugs
index 2d0fffd122ce..adf4042ba7f8 100644
--- a/Documentation/translations/zh_CN/SecurityBugs
+++ b/Documentation/translations/zh_CN/SecurityBugs
@@ -31,9 +31,9 @@ linux内核安全团队可以通过email<security@kernel.org>来联系。这是
一组独立的安全工作人员，可以帮助改善漏洞报告并且公布和取消一个修复。安
全团队有可能会从部分的维护者那里引进额外的帮助来了解并且修复安全漏洞。
当遇到任何漏洞，所能提供的信息越多就越能诊断和修复。如果你不清楚什么
-是有帮助的信息，那就请重温一下admin-guide/reporting-bugs.rst文件中的概述过程。任
-何攻击性的代码都是非常有用的，未经报告者的同意不会被取消，除非它已经
-被公布于众。
+是有帮助的信息，那就请重温一下admin-guide/reporting-issues.rst文件中的
+概述过程。任何攻击性的代码都是非常有用的，未经报告者的同意不会被取消，
+除非它已经被公布于众。
2) 公开
--
2.25.1
next reply other threads:[~2021-05-06 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 8:32 Wan Jiabing [this message]
2021-05-07 1:56 ` [PATCH] docs/zh_CN: make reporting-bugs.rst obsolete teng sterling
2021-05-07 2:24 ` Wu X.C.
2021-05-08 1:51 ` teng sterling
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=20210506083207.15705-1-wanjiabing@vivo.com \
--to=wanjiabing@vivo.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=kael_w@yeah.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;
as well as URLs for NNTP newsgroup(s).