Messages in this thread | | | Date | Thu, 14 Jul 2011 00:48:20 +0200 (CEST) | From | Jiri Kosina <> | Subject | Re: [PATCH 1/6] sched: Fix (harmless) typo 'CONFG_FAIR_GROUP_SCHED' |
| |
On Thu, 14 Jul 2011, Peter Zijlstra wrote:
> > For example pine, mutt and thunderbird (and the later two I almost never > > launch) all show everything correctly for me. > > > > Basically whatever you have in place on your side seems to violate RFC > > 2047, which shouldn't cause problems to anybody these days. > > > > Really seems like misconfiguration on your side. > > They show the utf8 string without problems, but calling any one of them > a decent MUA is far beyond where I can go, they're barely usable piles > of crap.
Umm, so? :)
> > > > git-am can also apply such thing without any problems with proper accents. > > > > > > that's assuming I actually use git at that stage, I find git to be an > > > utter pain to gather patches with. > > > > Okay, event quilt doesn't chuckle on that patch. > > I'm sure, quilt doesn't care about what's before the --- line, and in > fact they applied just fine. > > But my cobbled together script doesn't do horrid utf8 demunging and thus > had this terrible mess as a From: field. > > Also isn't the kernel source in LANG=C (aka ASCII?).
The sources are one thing (and even that doesn't hold ... for example a lot of places hold copyright sign that is not '(C)' but this UTF-8 thing). But the authorship/changelog information is a different story, right?
Just for code authors with non-ascii names:
$ git log | git shortlog -n | grep '^[^ ]' | grep -P "[\x80-\xFF]" | wc -l 245
(now admittedly some of those are results of broken scripts/systems such as yours, but most of them are valid).
Now, I have to finally add, I don't care a bit. At all. I just have been CCed -- for some odd reason -- on the original patch, and wanted to defend Jan against your 'wtf shitty crap you are sending' offenses, as he did absolutely nothing wrong (if at least RFCs and 99% of Internet can be taken as an etalon), and crap is IMHO located elsewhere :)
Thanks,
-- Jiri Kosina SUSE Labs
| |