Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 28 Apr 2023 17:42:12 +0100
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
Message-ID: <20230428-wired-germproof-5a243f7ef652@spud>
References: <20230428091018.1558-1-wangdeming@inspur.com>
 <71c91ae5-2ed7-cfd5-7b7f-6cb5a0141816@gmail.com>
 <871qk4awn2.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="obG4pUMAARmeQell"
Content-Disposition: inline
In-Reply-To: <871qk4awn2.fsf@meer.lwn.net>
Precedence: bulk


--obG4pUMAARmeQell
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 28, 2023 at 08:50:41AM -0600, Jonathan Corbet wrote:
> Akira Yokosawa <akiyks@gmail.com> writes:
>=20
> > 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=3D"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=3DUTF-8
>=20
> 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-Encod=
ing.
| 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.

--obG4pUMAARmeQell
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZEv3VAAKCRB4tDGHoIJi
0kJkAQD+44cVTxgqSXpoCUoSxBzU3k3Oo33DODhUh67TK+NPCAEA9Lo1mwZSg3p7
VbDlhPJilTVYUn55dpUTXxJBhYxx6gg=
=O4fM
-----END PGP SIGNATURE-----

--obG4pUMAARmeQell--