From: Jesper Juhl <jju@dif.dk>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: Linux 2.4.18 - the missing patch issue
Date: Mon, 25 Feb 2002 23:48:02 +0100 [thread overview]
Message-ID: <3C7ABF22.2030705@dif.dk> (raw)
> > 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
> >
>
> Does anyone know how long this bug has been in the kernel?
>
> If it's an old bug, 2.4.19-pre1 already has the fix, just like rc4
> did...
>
> This *one* bug isn't big enough to hurry, IMO.
You are probably right, a resonably harmless bug should not be enough to
justify a rushed 2.4.19 release. But the confusion and "bad publicity"
/might/ justify it.
I personally don't think that the publicity issue is something that the
kernel people should be concerned about, but user confusion probably is
- confused users submitting bug reports and/or patches against two
different 2.4.18 versions sounds to me like something that you want to
keep to a minimum, and the only way I see of removing that confusion is
to get 2.4.18 out of the way and replaced with 2.4.19 as soon as possible.
- Jesper Juhl - jju@dif.dk -
next reply other threads:[~2002-02-25 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 22:48 Jesper Juhl [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 22:25 Linux 2.4.18 - the missing patch issue Jesper Juhl
2002-02-25 22:34 ` Mike Fedyk
2002-02-25 22:39 ` Robert Love
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=3C7ABF22.2030705@dif.dk \
--to=jju@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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