public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: deleting 2.4.22 and 2.4.24 ACPI patches
Date: 17 Mar 2004 01:24:39 -0500	[thread overview]
Message-ID: <1079504678.2559.48.camel@dhcppc4> (raw)

Currently I supply the latest ACPI on

2.4.22
2.4.24
2.4.25
2.5.26

The reasoning is that 2.4 is the installed base and we want to make it
easy to patch the installed base with the latest ACPI -- so we bend over
backwards somewhat.

2.6.4
2.6.5

The reasoning is that there is no 2.6 installed base, so we want to
encourage using the latest release.  So support just the most recent
frozen release plus the release that is currently under development.
eg. when 2.6.6 opens, 2.6.4 will be deleted.

When the releases are similar, this is pretty easy to do; but when they
diverge, real work is required, including merging, testing etc.

So I'd like to delete 2.4.22 and 2.4.24 support.  When 2.4.26 closes,
I'll delete 2.4.25 too.

Let me know if this is a problem for you.

thanks,
-Len




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

             reply	other threads:[~2004-03-17  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17  6:24 Len Brown [this message]
     [not found] ` <1079504678.2559.48.camel-D2Zvc0uNKG8@public.gmane.org>
2004-04-13 18:23   ` deleting 2.4.22 and 2.4.24 ACPI patches Len Brown

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=1079504678.2559.48.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