linux-kernel - Re: [PATCH] Documentation/translations/ja

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: <871qk4awn2.fsf@meer.lwn.net>
Date:   Fri, 28 Apr 2023 08:50:41 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Akira Yokosawa <akiyks@...il.com>, wangdeming@...pur.com
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        shibata@...uxfoundation.org
Subject: Re: [PATCH] Documentation/translations/ja_JP/SubmittingPatches: fix
 some typos

Akira Yokosawa <akiyks@...il.com> writes:

> Your patch is rejected by "git am".
>
> In the header part of your email, I see these fields:
>
>> X-Mailer: git-send-email 2.31.1
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset="y"
>> Content-Transfer-Encoding: 8bit
>
> This looks broken.
> Please make sure your email header has a proper Content-Type
> as shown below:
>
>     Content-Type: text/plain; charset=UTF-8

This something that git send-email does on occasion; it's truly
obnoxious, and I have no idea why.  I end up fixing up patches by hand
when I see it.  If the change itself is OK, I can manage it from here.

Thanks,

jon