mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: David Relson <relson@osagesoftware.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17-rc1
Date: Sun, 16 Dec 2001 17:40:46 +0100	[thread overview]
Message-ID: <20011216174046.F5235@khan.acc.umu.se> (raw)
In-Reply-To: <4.3.2.7.2.20011216103506.00d94b90@mail.osagesoftware.com> <Pine.LNX.4.20.0112160810060.7801-100000@otter.mbay.net> <4.3.2.7.2.20011216111939.00e1eed0@mail.osagesoftware.com>
In-Reply-To: <4.3.2.7.2.20011216111939.00e1eed0@mail.osagesoftware.com>; from relson@osagesoftware.com on Sun, Dec 16, 2001 at 11:22:53AM -0500

On Sun, Dec 16, 2001 at 11:22:53AM -0500, David Relson wrote:
> At 11:10 AM 12/16/01, John Alvord wrote:
> >You shouldn't fix every single defect, just the ones with wide
> >impact. Otherwise the rcX series could go on a long time. john
> 
> John,
> 
> Well said.  Fix the show stoppers in the rcX series for 2.4.17.  Leave the 
> small ones for 2.4.18-preX.
> 
> ... repeat above steps for 2.4.18-rcX and 2.4.19
> ... repeat for ...
> 
> ... iterate until time for 2.6.0 :-)

Uhm, hopefully the release of 2.6.0 won't mean that maintainance of
2.4.xx will cease. While it *might* be possible that 2.4.xx is bugfree
enough, some smaller fixes and driver-backports will probably still
be needed.


Regards: David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-12-16 16:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 20:44 Marcelo Tosatti
2001-12-13 23:33 ` Ken Brownfield
2001-12-14  1:35 ` Roger Larsson
     [not found] ` <20011214061842.948118A6BA@cx518206-b.irvn1.occa.home.com>
2001-12-14 11:53   ` [BUG] 2.4.17-rc1 still has I/O freezing bug Ken Brownfield
2001-12-16  4:59 ` Linux 2.4.17-rc1 Daniel Phillips
2001-12-17 16:51   ` Marcelo Tosatti
2001-12-17 18:17   ` Richard Gooch
2001-12-17 21:00     ` Marcelo Tosatti
2001-12-16 14:13 ` David Relson
2001-12-16 14:19   ` Rik van Riel
2001-12-16 14:26   ` Dave Jones
2001-12-16 15:32     ` Ed Tomlinson
2001-12-16 15:37   ` David Relson
2001-12-16 16:10     ` John Alvord
2001-12-16 16:22     ` David Relson
2001-12-16 16:40       ` David Weinehall [this message]
2001-12-16 20:28   ` J Sloan
2001-12-18  1:27 ` Erik Andersen
2001-12-18  1:38   ` Dave Jones
2001-12-18  1:46     ` Erik Andersen
2001-12-18  1:53       ` Dave Jones
2001-12-14  1:18 Dieter Nützel
2001-12-16 19:25 Mario Vanoni
2001-12-17 11:30 Martin Knoblauch

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=20011216174046.F5235@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=relson@osagesoftware.com \
    /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

all inboxes | Powered by JetHome®