git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Marius Storm-Olsen <marius@trolltech.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: Broken umlaut in my name, again
Date: Mon, 6 Apr 2009 15:40:35 +0200	[thread overview]
Message-ID: <adf1fd3d0904060640k3fcac0d5oc09dde7ebd430231@mail.gmail.com> (raw)
In-Reply-To: <20090406131747.GH20356@atjola.homenet>

2009/4/6 Björn Steinbrink <B.Steinbrink@gmx.de>:
> On 2009.04.06 14:46:43 +0200, Santi Béjar wrote:
>> 2009/4/6 Björn Steinbrink <B.Steinbrink@gmx.de>:
>> > On 2009.03.31 17:30:39 +0200, Björn Steinbrink wrote:
>> >> While it makes no sense to map some email address to an empty one, doing
>> >> things the other way around can be useful. For example when using
>> >> filter-branch with an env-filter that employs a mailmap to fix up an
>> >> import that created such broken commits with empty email addresses.
>> >>
>> >> Signed-off-by: Björn Steinbrink <B.Steinbrink@gmx.de>
>> >
>> > The umlaut (ö) in my name is broken in the commit that made it into
>> > git.git --> 5288dd58356e53d61e2b3804fc7d8d23c3a46ab3
>> >
>> > Last time this happened when I used format-patch -s instead of commit -s
>> > IIRC. But since then, I pay attention to do the sign-off via commit -s,
>> > yet my name is broken again. What did I do wrong this time?
>>
>> I don't see nothing wrong in your mails. It appears to be a double
>> conversion to UTF-8 between the mail and the commit.
>>
>> But I always use format-patch -s without problems, what was your
>> problem with format-patch?
>
> I don't recall the exact problem, and I can't find the mails anymore,
> the IIRC it was something about Content-type being generated from the
> original commit message, and only afterwards the sign-off line got
> added, or something like that. That causes the Content-type to say
> ascii, although the sign-off had UTF-8 in it. Or something like that.
> Might very well have been fixed since then

Yes, it is fixed (at least what you described).

> (it was almost 2 years ago
> that I hit that bug IIRC),

Uf! half an eternity in git scale ;-)

Santi

  reply	other threads:[~2009-04-06 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 15:30 [PATCH] Mailmap: Allow empty email addresses to be mapped Björn Steinbrink
2009-04-06 11:46 ` Broken umlaut in my name, again Björn Steinbrink
2009-04-06 12:46   ` Santi Béjar
2009-04-06 13:17     ` Björn Steinbrink
2009-04-06 13:40       ` Santi Béjar [this message]
2009-04-06 16:47   ` Jeff King
2009-04-06 19:28     ` Björn Steinbrink

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=adf1fd3d0904060640k3fcac0d5oc09dde7ebd430231@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=B.Steinbrink@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=marius@trolltech.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).