From: Andy Whitcroft <apw@shadowen.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: Warning: commit message does not conform to UTF-8. (mmotm "10-Nov-2007 22:46")
Date: Mon, 12 Nov 2007 09:01:54 +0000 [thread overview]
Message-ID: <20071112090136.GF301@shadowen.org> (raw)
In-Reply-To: <200711110030.lAB0UvLx006968@agora.fsl.cs.sunysb.edu>
On Sat, Nov 10, 2007 at 07:30:57PM -0500, Erez Zadok wrote:
> Andrew,
>
> I'm getting minor warnings when applying two patches from
> <http://userweb.kernel.org/~akpm/mmotm/>
>
> It's probably not serious but I wonder if checkpatch catches this.
>
> Applying patch..git-net.patch
> Warning: commit message does not conform to UTF-8.
> You may want to amend it after fixing the message, or set the config
> variable i18n.commitencoding to the encoding your project uses.
>
> Applying patch..mnt_unbindable-fix.patch
> Warning: commit message does not conform to UTF-8.
> You may want to amend it after fixing the message, or set the config
> variable i18n.commitencoding to the encoding your project uses.
We do have checks for UTF-8. The commit message problems are usually real
names in Signed-off-by:s being "complex" and being in their email locale
not UTF-8. It is a problem area for sure as people want their email to
look right in their email to the list, and yet they need it in UTF-8 for git.
Yeah it looks like we pick it up ok, the message could do with a little
love:
apw@pinky$ ~/git/checkpatch/checkpatch.pl -q --no-tree ./git-net.patch
ERROR: Invalid UTF-8
#229:
This is based on a patch by Vicenç Beltran Querol.
ERROR: Invalid UTF-8
#398:
by Toralf Förster:
ERROR: Invalid UTF-8
#773:
Signed-off-by: Lutz Preßler <Lutz.Pressler@SerNet.DE>
-apw
prev parent reply other threads:[~2007-11-12 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 0:30 Warning: commit message does not conform to UTF-8. (mmotm "10-Nov-2007 22:46") Erez Zadok
2007-11-12 9:01 ` Andy Whitcroft [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=20071112090136.GF301@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.