From: Alex Shi <seakeel@gmail.com>
To: Wu XiangCheng <bobwxc@email.cn>, Alex Shi <alexs@kernel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
YanTeng Si <sterlingteng@gmail.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/zh_CN: sync reporting-issues.rst
Date: Tue, 13 Apr 2021 15:02:40 +0800 [thread overview]
Message-ID: <9c97944e-7a0c-8777-5be0-133a0f104afd@gmail.com> (raw)
In-Reply-To: <20210408135659.GA6747@bobwxc.top>
Nice work!
On 2021/4/8 下午9:57, Wu XiangCheng wrote:
>
>
> 为什么有些问题在报告后没有任何回应或仍未解决？
> @@ -1267,3 +1333,4 @@ FLOSS 问题报告的人看，询问他们的意见。同时征求他们关于
> 向 Linux 内核开发者报告问题是很难的：这个文档的长度和复杂性以及字里行间的内
> 涵都说明了这一点。但目前就是这样了。这篇文字的主要作者希望通过记录现状来为
> 以后改善这种状况打下一些基础。
> +
Do we need a empty line? except this point:
Reviewed-by: Alex Shi <alexs@kernel.org>
next prev parent reply other threads:[~2021-04-13 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 13:57 [PATCH] docs/zh_CN: sync reporting-issues.rst Wu XiangCheng
2021-04-08 15:14 ` Wu X.C.
2021-04-13 7:02 ` Alex Shi [this message]
2021-04-13 7:29 ` [PATCH v2] " Wu XiangCheng
2021-04-13 21:07 ` Jonathan Corbet
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=9c97944e-7a0c-8777-5be0-133a0f104afd@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.com \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mchehab+huawei@kernel.org \
--cc=sterlingteng@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).