[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230428-wired-germproof-5a243f7ef652@spud>
Date: Fri, 28 Apr 2023 17:42:12 +0100
From: Conor Dooley <conor@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Akira Yokosawa <akiyks@...il.com>, wangdeming@...pur.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
shibata@...uxfoundation.org
Subject: Re: [PATCH] Documentation/translations/ja_JP/SubmittingPatches: fix
some typos
On Fri, Apr 28, 2023 at 08:50:41AM -0600, Jonathan Corbet wrote:
> 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.
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.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists