From: Johannes Sixt <j.sixt@viscovery.net>
To: Tor Arvid Lund <torarvid@gmail.com>
Cc: Jeff King <peff@peff.net>, Git mailing list <git@vger.kernel.org>
Subject: Re: A little mystery - crash caused by empty commit message.
Date: Tue, 10 Feb 2009 12:46:38 +0100 [thread overview]
Message-ID: <4991691E.6010808@viscovery.net> (raw)
In-Reply-To: <20090210113234.GE12089@coredump.intra.peff.net>
Jeff King schrieb:
> It _is_ generally hard to get an empty commit message using "git
> commit". But it's possible there is a bug in cherry-pick, rebase, or
> some ohter low-level tool that accidentally erased your message
> as the commit was moved.
Since this is on Windows, chances are that this is an encoding issue. If
you have non-ASCII in the commit message, but i18n.commitEncoding is
unset, then you can introduce invalid UTF8 sequences easily. This could
confuse one of the pipelines (rebase, am, cherry-pick, etc).
You should set
git config i18n.commitencoding cp1252
(or whatever is appropriate for you locale). I even have
git config i18n.logoutputencoding cp850
so that I see correct umlauts if I happen to run git log without a pager
in CMD ;) (I rarely do that, though.)
-- Hannes
next prev parent reply other threads:[~2009-02-10 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 11:15 A little mystery - crash caused by empty commit message Tor Arvid Lund
2009-02-10 11:32 ` Jeff King
2009-02-10 11:46 ` Johannes Sixt [this message]
2009-02-10 12:58 ` Tor Arvid Lund
2009-02-10 15:30 ` Jeff King
2009-02-16 10:18 ` Tor Arvid Lund
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=4991691E.6010808@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=torarvid@gmail.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;
as well as URLs for NNTP newsgroup(s).