From: Jeff King <peff@peff.net>
To: "René Haber" <rene@habr.de>
Cc: Thomas Rast <trast@inf.ethz.ch>, git@vger.kernel.org
Subject: Re: Bug: pull --rebase with é in name
Date: Mon, 5 Mar 2012 06:58:15 -0500 [thread overview]
Message-ID: <20120305115815.GA4550@sigill.intra.peff.net> (raw)
In-Reply-To: <F5A485EA-7EAD-4D8B-87C4-7185F713318C@habr.de>
On Mon, Mar 05, 2012 at 12:42:14PM +0100, René Haber wrote:
> I'm running git 1.7.9.2 from Fink Project on MacOS X 10.6.
> The gitconfig in hex is attached.
Hmm, looks like pretty standard utf8:
0000020: 6d65 203d 2052 656e c3a9 2048 6162 6572 me = Ren.. Haber
and the same thing I used in my tests. I tried repeating the test with
v1.7.9.2 on OS X (although my test box is 10.7), and couldn't replicate
it.
Can you show us the commit that causes the problem, as printed by "git
cat-file commit $commit | xxd"? I just want to double-check that there
are no odd bytes there.
Also, what happens if you do:
sh -c '
. /sw/lib/git-core/git-sh-setup
get_author_ident_from_commit $commit
'
(my theory is that this is the underlying problem in the rebase, and
should show the bug; by narrowing it down, it should make testing a lot
simpler).
-Peff
next prev parent reply other threads:[~2012-03-05 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 9:59 Bug: pull --rebase with é in name René Haber
2012-03-05 10:26 ` Jeff King
2012-03-05 10:37 ` Thomas Rast
2012-03-05 11:42 ` René Haber
2012-03-05 11:58 ` Jeff King [this message]
2012-03-05 12:36 ` Jakub Narebski
2012-03-05 12:46 ` René Haber
2012-03-05 13:04 ` Thomas Rast
2012-03-05 13:19 ` René Haber
2012-03-05 13:29 ` Jeff King
2012-03-05 13:40 ` Thomas Rast
2012-03-05 13:50 ` Jeff King
2012-03-05 17:23 ` Junio C Hamano
2012-03-06 8:23 ` Jeff King
2012-03-06 8:36 ` Thomas Rast
2012-03-06 9:02 ` Jeff King
2012-03-06 18:31 ` Junio C Hamano
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=20120305115815.GA4550@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=rene@habr.de \
--cc=trast@inf.ethz.ch \
/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).