From: Conor Dooley <conor@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Akira Yokosawa <akiyks@gmail.com>,
wangdeming@inspur.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, shibata@linuxfoundation.org
Subject: Re: [PATCH] Documentation/translations/ja_JP/SubmittingPatches: fix some typos
Date: Fri, 28 Apr 2023 17:42:12 +0100 [thread overview]
Message-ID: <20230428-wired-germproof-5a243f7ef652@spud> (raw)
In-Reply-To: <871qk4awn2.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Fri, Apr 28, 2023 at 08:50:41AM -0600, Jonathan Corbet wrote:
> Akira Yokosawa <akiyks@gmail.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.
If you have special characters in your patch/cover, git send-email will
prompt you to declare a encoding. The message is something like:
| The following files are 8bit, but do not declare a Content-Transfer-Encoding.
| 0000-cover-letter.patch
| Which 8bit encoding should I declare [UTF-8]?
It's very easy to assume that pressing y to accept UTF-8 is the right
thing to do, rather than pressing enter for the default.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-04-28 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 9:10 [PATCH] Documentation/translations/ja_JP/SubmittingPatches: fix some typos Deming Wang
2023-04-28 14:45 ` Akira Yokosawa
2023-04-28 14:50 ` Jonathan Corbet
2023-04-28 15:14 ` Akira Yokosawa
2023-04-28 16:42 ` Conor Dooley [this message]
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=20230428-wired-germproof-5a243f7ef652@spud \
--to=conor@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shibata@linuxfoundation.org \
--cc=wangdeming@inspur.com \
/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