linux-kernel - Re: [PATCH] crypto: convert crypto.h to UTF-8

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]

Date:	03 May 2007 13:53:16 +0200
From:	Arne Georg Gleditsch <argggh@...phinics.no>
To:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
Cc:	Herbert Xu <herbert@...dor.apana.org.au>,
	linux-kernel@...r.kernel.org, trivial@...nel.org,
	davem@...emloft.net, linux-crypto@...r.kernel.org
Subject: Re: [PATCH] crypto: convert crypto.h to UTF-8

"John Anthony Kazos Jr." <jakj@...-k-j.com> writes:
> Did this file individually, per request. Will re-do the whole tree later 
> as I'm still working on my handy-dandy testing and patching tools and 
> don't have a lot of time outside of work until the summer gets underway.

While this is probably inevitable, it would be nice if there was some
way to determine the actual coding system used for individual files.
Especially if we're mixing latin1 and utf8 in the same tree.  Has
something like adding "/* -*- coding: utf-8; -*- */" or similar to the
top of converted files been considered?

-- 
								Arne.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/