public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jju@dif.dk>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.18 - the missing patch issue
Date: Mon, 25 Feb 2002 23:25:25 +0100	[thread overview]
Message-ID: <3C7AB9D5.9080906@dif.dk> (raw)

Ok, so 2.4.18 was released without a fix that onyl matters to a very 
limited number of Linux users, while that's not perfect it's not the end 
of the world either.

A few different solutions have been suggested :

1) People have suggested releasing a new 2.4.18 emidiately which 
includes the missing fix.
2) Someone proposed to release 2.4.19 imidiately which would be 2.4.18 + 
the missing fix.
3) Some people just want to forget about it ;)

All 3 are IMVHO bad ideas for these reasons; nr. 1 would create 
confusion by having two different versions of 2.4.18 floating around. 
nr. 2 would probably also cause some minor degree of confusion amongst 
users and would also give the (wrong) impression that Linux kernel 
releases are not thoroughly tested. I'll not comment on 3 ;)

I suggest that instead of the previously proposed solutions an effort 
should instead be made to release 2.4.19 relatively fast. Instead of 
including a lot of fixes, only include the most critical known fixes in 
2.4.19-pre1 (and maybe -pre2), then go to -rc1 as soon as possible and 
get 2.4.19 out the door pretty fast with important fixes and leave all 
other stuff for 2.4.20-pre1


Just my 0.02 euro-cent


- Jesper Juhl - jju@dif.dk -



             reply	other threads:[~2002-02-25 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 22:25 Jesper Juhl [this message]
2002-02-25 22:34 ` Linux 2.4.18 - the missing patch issue Mike Fedyk
2002-02-25 22:39   ` Robert Love
  -- strict thread matches above, loose matches on Subject: below --
2002-02-25 22:48 Jesper Juhl

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=3C7AB9D5.9080906@dif.dk \
    --to=jju@dif.dk \
    --cc=linux-kernel@vger.kernel.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