From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: Henrik Brix Andersen <brix-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Missing acpi-20050101-2.6.10 patch?
Date: Fri, 7 Jan 2005 09:56:05 +0100 [thread overview]
Message-ID: <20050107085605.GA19136@fuchi> (raw)
In-Reply-To: <1105040016.11930.11.camel-7g89Hwo0MwsWlyYapE9R8Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
hello Henrik..
* Henrik Brix Andersen <brix-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> [2005-01-07 09:45 +0100]:
>
> A new release of the acpi patch dating 2005-01-01 was announced at
> http://acpi.sf.net, but it is not present in the download directory at
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.10/
>
> The latest patch available at the above mentioned ftp site is dated
> 2004-12-10 and doesn't contain any patch - only a ChangeSet list.
>
> Where can I find the lastest ACPI patch?
acpi-20050101-2.6.10 does not exist. the date given in that filename is
not the date of the release of the patch but the date of the release of
the ACPI-CA implemented by that patch. besides the latest ACPI-CA, a
patch also includes Linux-specific code. please correct me, if i am
wrong, Len. :)
Len released yet another patch yesterday, go download:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.10/acpi-20041210-2.6.10.diff.bz2
hth,
Sebastian
--
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-07 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 19:33 Missing acpi-20050101-2.6.10 patch? Henrik Brix Andersen
[not found] ` <1105040016.11930.11.camel-7g89Hwo0MwsWlyYapE9R8Q@public.gmane.org>
2005-01-07 8:56 ` Sebastian Henschel [this message]
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=20050107085605.GA19136@fuchi \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=brix-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.