From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: ACPI patch status (now consistent;-)
Date: 16 Aug 2004 20:02:25 -0400 [thread overview]
Message-ID: <1092700945.23066.62.camel@dhcppc4> (raw)
I publish the latest ACPI patch* against 4 trees:
2.6 latest released (now 2.6.8)
2.6 development tree (now 2.6.9)
2.4 latest released (now 2.4.27)
2.4 development tree (now 2.4.28)
The patch is published in 2 formats, BK and plain patch:
http://linux-acpi.bkbits.net/
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/
Further, there are two versions of each tree. The *test* trees are the
latest bleeding edge. Note that Andrew pulls linux-acpi-test-2.6.* into
the -mm tree. I reserve the right to remove csets from the test trees
for patches that do not work out.
The linux-acpi-release* trees are what the kernel.org release/ plain
patches are generated from, and these are staging areas for pulls into
Marcelo's 2.4 and Linus' 2.6 baseline trees.
Sorry these trees were in flux earlier today, they should all be
consistent now. If you have any troubles or suggestions, please let me
know.
thanks,
-Len
*Only critical configuration fixes are back-ported to 2.4 at this point.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
reply other threads:[~2004-08-17 0:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1092700945.23066.62.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox