lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AEgA2wDqDe0-PVocRYFgJaoK.3.1601276385471.Hmail.bailu.lin@vivo.com>
Date:   Mon, 28 Sep 2020 14:59:45 +0800 (GMT+08:00)
From:   林白鹭 <bailu.lin@...o.com>
To:     Alex Shi <alex.shi@...ux.alibaba.com>
Cc:     Jonathan Corbet <corbet@....net>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>,
        Harry Wei <harryxiyou@...il.com>,
        linux-arm-kernel@...ts.infradead.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, kernel@...o.com,
        Wang Qing <wangqing@...o.com>
Subject: Re:Re: [PATCH] Documentation: Chinese translation of Documentation/arm64/perf.rst

>在 2020/9/27 上午4:15, Jonathan Corbet 写道:
>> On Sat, 26 Sep 2020 22:35:51 +0800
>> Alex Shi <alex.shi@...ux.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.
>

Sorry for bringing trouble. I used 'git send-email' with UTF-8, also built with 
'make htmldocs'. I think that caused by two patches(translation of 
Documentation/arm64/hugetlbpage.rst and Documentation/arm64/perf.rst)
sequence, hugetlbpage first perf.rst second. It's my mistake,I'll send with patch
Series for this two patch.

Thanks
Bailu

>Thanks
>Alex
>



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ