[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080113.235113.170762359.davem@davemloft.net>
Date: Sun, 13 Jan 2008 23:51:13 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: ilpo.jarvinen@...sinki.fi
Cc: herbert@...dor.apana.org.au, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs
From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
Date: Mon, 14 Jan 2008 09:43:08 +0200 (EET)
> So which test case you prefer? :-) Is iso-8859-1 from+content ok? Or
> should I keep trying to live with mixed utf-8 which I didn't got even
> fully working last time because git-send-email is probably either too dumb
> or too intelligent (I'm not even sure which), but you were able correct it
> by your tools so the flawed signed-off never entered to the git logs as
> incorrectly formatted :-).
>
> I'd prefer sending them as iso-8859-1 compliant (and I guess you are able
> to test your fix-to-utf-8 machinery with it as well :-)), as it would also
> make my mails compatible with other people's git apply tools you're not
> using (otherwise I'd probably forget to change it occassionally when
> interacting with others than you).
For now either way is fine with me. If the situation changes I'll
let you know.
I'm surprised git-send-email can't get it purely utf8 correctly.
I wonder if there is some issue with how it gets your name
string for the commit author etc.
I wonder if getting it into your global GIT config file in proper
UTF8 encoding would fix things.
Put something like this into ~/.gitconfig
--------------------
[user]
name = Ilpo Järvinen
email = ilpo.jarvinen@...sinki.fi
--------------------
The GIT maintainer is Finnish which makes this situation even
more perplexing to me, you might want to discuss it with him :-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists