From: Alex Shi <alex.shi@linux.alibaba.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Bailu Lin <bailu.lin@vivo.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Harry Wei <harryxiyou@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@vivo.com,
Wang Qing <wangqing@vivo.com>
Subject: Re: [PATCH] Documentation: Chinese translation of Documentation/arm64/perf.rst
Date: Sun, 27 Sep 2020 10:12:17 +0800 [thread overview]
Message-ID: <8d7eec7d-5a62-9cc6-75de-10490b999e7a@linux.alibaba.com> (raw)
In-Reply-To: <20200926141547.0ef26bdb@lwn.net>
在 2020/9/27 上午4:15, Jonathan Corbet 写道:
> On Sat, 26 Sep 2020 22:35:51 +0800
> Alex Shi <alex.shi@linux.alibaba.com> wrote:
>
>> Why your patch repeatly has encoding issue which fails on 'git am'
>> Could you like to check the problem before send out?
>> Could you please fix your editor issue by Documentation/process/email-clients.rst
>> or send patch by git send-email.
>>
>> And please don't waste other time on meaningless issue again!
>
> The way to be sure you have solved this kind of problem is to first email
> the patch to you, then be sure that what you receive can be applied.
> Please get to the point where that works, then I'll be glad to apply your
> translations.
>
CC Qing,
There are few documents of how to join the community development
https://www.kernel.org/doc/html/latest/translations/zh_CN/index.html
Shortly, sth could be summaried as following in pariticular documents.
1, setup well your email client, to be sure all your patch from your email system
could be applied by 'git am'. Current email client often cover the endcoding issue
but git will failed on that.
2, 'make help' show couple of doc related options:
htmldocs - HTML
latexdocs - LaTeX
pdfdocs - PDF
epubdocs - EPUB
xmldocs - XML
linkcheckdocs - check for broken external links
(will connect to external hosts)
refcheckdocs - check for references to non-existing files under
Documentation
cleandocs - clean all generated files
Do 'make linkcheckdocs/refcheckdocs/htmldocs', and check if the result works as
expected, of course it would be better if you can make/check all type docs, but
at least finish above 3 kinds of checks.
3, As to related docs, sending them as a couple series could help people retrieve
easy.
looking forward for your new translation docs.
Thanks
Alex
> Thanks,
>
> jon
>
next prev parent reply other threads:[~2020-09-27 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 10:22 Bailu Lin
2020-09-26 14:35 ` Alex Shi
2020-09-26 20:15 ` Jonathan Corbet
2020-09-27 2:12 ` Alex Shi [this message]
2020-09-28 6:59 ` 林白鹭
2020-10-28 13:48 Bailu Lin
2020-10-29 5:55 ` Alex Shi
2020-10-29 15:14 Bailu Lin
2020-10-30 2:33 ` Alex Shi
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=8d7eec7d-5a62-9cc6-75de-10490b999e7a@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=bailu.lin@vivo.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=kernel@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangqing@vivo.com \
--cc=will@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
Powered by JetHome