From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Jeff King <peff@peff.net>
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 21:28:48 +0200 [thread overview]
Message-ID: <20090406192848.GJ20356@atjola.homenet> (raw)
In-Reply-To: <20090406164732.GA11724@sigill.intra.peff.net>
On 2009.04.06 12:47:33 -0400, Jeff King wrote:
> On Mon, Apr 06, 2009 at 01:46:18PM +0200, Björn Steinbrink wrote:
>
> > 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
>
> The mail you sent that presumably became 5288dd58 looks fine (both the
> >From and body are properly marked as iso8859-1), and "git am" applies it
> correctly here. I wonder if Junio did something unusual while applying.
Hm, ok, so I take it that it wasn't me who broke things. Then I'm
already happy. I don't care much about my name being messed up, but just
wanted to make sure that it wasn't my fault.
Thanks,
Björn
prev parent reply other threads:[~2009-04-06 19:30 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
2009-04-06 16:47 ` Jeff King
2009-04-06 19:28 ` Björn Steinbrink [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=20090406192848.GJ20356@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marius@trolltech.com \
--cc=peff@peff.net \
/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