From: Jeff Garzik <jgarzik@pobox.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.x ACPI updates
Date: Mon, 18 Aug 2003 17:10:03 -0400 [thread overview]
Message-ID: <3F4140AB.8020605@pobox.com> (raw)
In-Reply-To: <20030818205529.GC18599@werewolf.able.es>
J.A. Magallon wrote:
> On 08.18, Jeff Garzik wrote:
>
>>For those without BK, I have extracted Intel's latest 2.4.x ACPI updates
>>into patch form:
>>
>>ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.4/2.4.22-rc2-acpi1.patch.bz2
>
>
> The patch has some strange non-ascii chars there:
> - the first hunk changes a don't to a don't (an apostrophe to a non-ascii
> acute accent...)
> - A für to a für (I see the current fine on a terminal but not the second)
> - Some copyright symbols...
>
> See the 1st, 3rd and 4th hunks in the changes to Configure.help.
Bug Intel, not me.
I personally think they shouldn't be changing non-ACPI-related
Configure.help entries at all, and what you point out was one of the
minor ACPI gaffs I mentioned to Marcelo and Alan.
Jeff
next prev parent reply other threads:[~2003-08-18 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 19:09 [patch] 2.4.x ACPI updates Jeff Garzik
2003-08-18 20:55 ` J.A. Magallon
2003-08-18 21:10 ` Jeff Garzik [this message]
2003-08-19 2:04 Brown, Len
2003-08-19 2:22 ` Jeff Garzik
2003-08-19 13:30 ` Alan Cox
2003-08-20 0:04 Brown, Len
2003-08-20 18:15 ` Marcelo Tosatti
2003-08-22 2:49 Brown, Len
2003-08-23 2:15 Brown, Len
[not found] <Pine.LNX.4.44.0308230015440.14227-100000@logos.cnet>
2003-08-23 17:26 ` Marcelo Tosatti
2003-08-23 21:05 Brown, Len
2003-08-23 21:30 ` Marcelo Tosatti
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=3F4140AB.8020605@pobox.com \
--to=jgarzik@pobox.com \
--cc=jamagallon@able.es \
--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).