From: Mike Fedyk <mfedyk@matchmail.com>
To: Jesper Juhl <jju@dif.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - the missing patch issue
Date: Mon, 25 Feb 2002 14:34:15 -0800 [thread overview]
Message-ID: <20020225223415.GA4393@matchmail.com> (raw)
In-Reply-To: <3C7AB9D5.9080906@dif.dk>
In-Reply-To: <3C7AB9D5.9080906@dif.dk>
On Mon, Feb 25, 2002 at 11:25:25PM +0100, Jesper Juhl wrote:
> 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.
Mike
next prev parent reply other threads:[~2002-02-25 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 22:25 Linux 2.4.18 - the missing patch issue Jesper Juhl
2002-02-25 22:34 ` Mike Fedyk [this message]
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=20020225223415.GA4393@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=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 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.