linux-kernel - Re: [PATCH 1/2] docs/zh_CN: sync with original text Documentation/vm/page

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <68b68f35-86e5-3f3b-ffd0-bea9c952fc66@meizu.com>
Date:   Tue, 26 Apr 2022 16:23:07 +0800
From:   baihaowen <baihaowen@...zu.com>
To:     Alex Shi <seakeel@...il.com>, <siyanteng01@...il.com>
CC:     <alexs@...nel.org>, <corbet@....net>, <linux-doc@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <siyanteng@...ngson.cn>
Subject: Re: [PATCH 1/2] docs/zh_CN: sync with original text
 Documentation/vm/page_owner.rst

在 4/26/22 4:20 PM, Alex Shi 写道:
>
> On 4/25/22 09:17, baihaowen wrote:
>> 在 4/24/22 11:16 AM, Alex Shi 写道:
>>> On 4/24/22 10:56, baihaowen wrote:
>>>>>> +        ======          ==========      ==================
>>>> hi, Alex
>>>> I can apply local.
>>>> ➜  linux-next git:(heads/next-20220421) ✗ git am doc_pageonwer_patches/0001-docs-zh_CN-sync-with-original-text-Documentation-vm-.patch
>>>> 应用：docs/zh_CN: sync with original text Documentation/vm/page_owner.rst
>>>> ➜  linux-next git:(heads/next-20220421) ✗ git am doc_pageonwer_patches/0002-doc-vm-page_owner.rst-Fix-table-display-confusion.patch   
>>>> 应用：doc/vm/page_owner.rst: Fix table display confusion
>>>>
>>>> I think git send-email will change format by my select. I'll try to resend.
>>> Send to yourself only then get it from your email client and try applying. 
>>>
>>> Thanks
>>> Alex
>> Hi Alex
>>
>> Could you tell me how do you do when you get a patch from email ?
>>
>> I get my patch from email and then copy-patse to a new file, then git am xx.patch.
> Don't do it. copy usually mess the format of patch.
>
> Saving the patch email from many kind of email-clients as raw file, like thunderbird etc.
> Then using 'git am xxx.patch'. It will work. In fact, git can handle the plain email patch well.
>
>
>> It will notice 补丁格式检测失败。
>>
hi, Alex
I have sent you an available patch set, plz try to apply.

-- 
Haowen Bai