From: Jeff Garzik <jgarzik@pobox.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: "J.A. Magallon" <jamagallon@able.es>, linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.x ACPI updates
Date: Mon, 18 Aug 2003 22:22:25 -0400 [thread overview]
Message-ID: <3F4189E1.5010808@pobox.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE009FC79@hdsmsx402.hd.intel.com>
Brown, Len wrote:
> The ISO_8859_1 acute accent, u with diaeresis, and registered sign, have been in Config.info since Feb 2002.
>
> Andy's tools seem to have extended them to 16-bit characters during a merge. A "minor gaff"? Okay, I guess that's fair. He promises that he doesn't know how to type a latin capital A with a circumflex on his keyboard;-).
>
> Moving on... Is the fix to restore the 8-bit characters, or use 7-bit characters?
Just sent a private message, but to relate the process to others as well...
The fix is to ensure that the ACPI updates sent to Marcelo never touch
areas of Documentation/Configure.help that do not relate to ACPI ;-)
Whatever characters are currently in Configure.help, just leave them be :)
Jeff, being a UTF8 fan, is pained saying this...
next prev parent reply other threads:[~2003-08-19 2:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 2:04 [patch] 2.4.x ACPI updates Brown, Len
2003-08-19 2:22 ` Jeff Garzik [this message]
2003-08-19 13:30 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 21:05 Brown, Len
2003-08-23 21:30 ` Marcelo Tosatti
[not found] <Pine.LNX.4.44.0308230015440.14227-100000@logos.cnet>
2003-08-23 17:26 ` Marcelo Tosatti
2003-08-23 2:15 Brown, Len
2003-08-22 2:49 Brown, Len
2003-08-20 0:04 Brown, Len
2003-08-20 18:15 ` Marcelo Tosatti
2003-08-18 19:09 Jeff Garzik
2003-08-18 20:55 ` J.A. Magallon
2003-08-18 21:10 ` Jeff Garzik
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=3F4189E1.5010808@pobox.com \
--to=jgarzik@pobox.com \
--cc=jamagallon@able.es \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).