linux-kernel - Re: [PATCH v2 1/3] zh_CN/CodingStyle: improve translation

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: <CAMcnyaw=n3dZZ+quS3OVh0Jak-0dbGHuxk6=Odgae8YKNvLKCQ@mail.gmail.com>
Date:   Fri, 27 Jan 2017 10:28:43 +0800
From:   Andy Deng <theandy.deng@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Mauro Carvalho Chehab <mchehab@...radead.org>
Subject: Re: [PATCH v2 1/3] zh_CN/CodingStyle: improve translation

2017-01-27 6:40 GMT+08:00 Jonathan Corbet <corbet@....net>:

> OK, I've applied the whole set, thanks.

Thanks for applying!

> One thing, though: your messages came through with this header:
>
>         Content-Type: text/plain; charset=y
>
> The screwy "charset=y" puts "git am" into a severely uncooperative mood,
> so I had to edit your messages by hand to apply them.   Mauro (copied), do
> I remember correctly that you figured out how that was happening to your
> emails? It would be good to get that understood, documented, and maybe
> even fixed...

Oh, I think I found the reason, it's my fault...

I used git send-email to send the patch set, git asked me:

        "Which 8bit encoding should I declare [UTF-8]?"

Then I pressed 'y' and hit 'Enter', thus, the header becomes:

        Content-Type: text/plain; charset=y

charset should be "UTF-8", not 'y'... I apologize for the mistake.

Today is Chinese New Year's Eve, have a nice day and give my best wishes
to you.

Thanks,
Andy