From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI patch flow
Date: 03 Feb 2004 08:01:29 -0500 [thread overview]
Message-ID: <1075813288.13729.45.camel@dhcppc4> (raw)
In-Reply-To: <20040203122832.GA1405-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
> > I'd like to stop maintaining (and delete) 2.4.23 -- with the release of
> > 2.4.24, I doubt anybody is using 2.4.23.
> >
> > I'd like to stop maintaining (and delete) 2.6.0 -- with the release of
> > 2.6.1, I doubt anybody is using 2.6.0. Also, 2.6.1 has diverged
> > somewhat from 2.6.0, so maintaining 2.6.0 has become problematic.
> >
> > let me know if you have any issues with this.
>
> I do not see any problems with that.
>
> For 2.6, if I were you, I'd drop 2.6.1, too. People should upgrade to
> latest if they have problems..
Encourage upgrades to the latest -- I agree. The downside, however, is
when the latest causes new problems -- so I'll keep 2.6.1 around for
comparisons until after 2.6.2 comes out. (or until divergence makes it a
pain to maintain;-)
Also, when we reach the point that distros base a release on 2.6, it is
useful to have a tree of the same vintage to make patching the distro
tree viable.
thanks,
-Len
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-03 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:46 ACPI patch flow Len Brown
[not found] ` <1075747579.2394.108.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-03 12:28 ` Pavel Machek
[not found] ` <20040203122832.GA1405-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-02-03 13:01 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-27 2:18 Brown, Len
2003-09-27 2:18 ` Brown, Len
2003-09-10 21:12 Brown, Len
2003-09-10 21:12 ` Brown, Len
2003-09-10 19:01 Brown, Len
2003-09-10 19:01 ` Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE009FD58-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-09-10 20:23 ` Jeff Garzik
2003-09-10 20:23 ` 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=1075813288.13729.45.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@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.