From: Arne Georg Gleditsch <argggh@dolphinics.no>
To: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, trivial@kernel.org,
davem@davemloft.net, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: convert crypto.h to UTF-8
Date: 03 May 2007 13:53:16 +0200 [thread overview]
Message-ID: <87r6pyqg2b.fsf@pelargir.dolphinics.no> (raw)
In-Reply-To: <alpine.DEB.0.98.0705030711020.17390@sigma.j-a-k-j.com>
"John Anthony Kazos Jr." <jakj@j-a-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.
next prev parent reply other threads:[~2007-05-03 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 17:25 [PATCH] crypto: convert "crypto" subdirectory to UTF-8 John Anthony Kazos Jr.
2007-04-18 9:33 ` Stefan Richter
2007-04-18 9:46 ` Alan Cox
2007-05-02 4:43 ` Herbert Xu
2007-05-02 9:56 ` John Anthony Kazos Jr.
2007-05-02 10:00 ` Herbert Xu
2007-05-03 11:17 ` [PATCH] crypto: convert crypto.h " John Anthony Kazos Jr.
2007-05-03 11:53 ` Arne Georg Gleditsch [this message]
2007-05-03 13:21 ` John Anthony Kazos Jr.
2007-05-03 13:52 ` Arne Georg Gleditsch
2007-05-03 14:32 ` John Anthony Kazos Jr.
2007-05-03 15:22 ` Jan Engelhardt
2007-05-03 15:35 ` John Anthony Kazos Jr.
2007-05-03 18:32 ` Jan Engelhardt
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=87r6pyqg2b.fsf@pelargir.dolphinics.no \
--to=argggh@dolphinics.no \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jakj@j-a-k-j.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/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