netdev - Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080112.202224.135071859.davem@davemloft.net>
Date:	Sat, 12 Jan 2008 20:22:24 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	ilpo.jarvinen@...sinki.fi, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Sat, 12 Jan 2008 23:17:40 +1100

> Your emails are now using UTF-8 encoding but it's still declaring
> ISO-8859-1 as the charset.  So you probably want to fix that up or
> your name may show up as JÃ¤vinen on the reader's screen.

Yes, for people using the GIT email patch applying tools, it might do
that.  However I believe there are options to git-am and friends to
force it to put things into UTF-8.

I ran into some problems with encoding because I apply stuff by hand
using scripts I wrote.

But those problem won't happen any more for me.

I'm now saving the commit message and patch into files explicitly in
emacs, and verifying the coding (with "C-h C RET") and if it's wrong I
fix it before saving with "C-x RET f mule-utf-8"

Then I feed those into my patch applying scripts.
--
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