From: Arjan van de Ven <arjanv@redhat.com>
To: Michael Knigge <Michael.Knigge@set-software.de>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Frank Cusack <fcusack@fcusack.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc8
Date: 12 Jun 2003 10:09:56 +0200 [thread overview]
Message-ID: <1055405396.5785.1.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030612.6274686@knigge.local.net>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Thu, 2003-06-12 at 08:27, Michael Knigge wrote:
>
> Hmmm... I don't want to tell you how you have to do your job, but this
> is a known error and (if I followed the postings here correctly) there
> was a fix posted. So why not include it in 2.4.22?
If you wait with releases until every last and final bug is fixed,
you'll never get a release out, because there is always SOME bug
somewhere left, the kernel is just too big for that to not be the case.
It's a matter of priorities if a defect is a stopship or not, and it
seems the bug in question isn't according to the release managers
opinion.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-12 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 22:06 Marcelo Tosatti
2003-06-10 23:56 ` Frank Cusack
2003-06-11 0:10 ` Marcelo Tosatti
2003-06-11 21:15 ` Marcelo Tosatti
2003-06-12 6:27 ` Michael Knigge
2003-06-12 7:56 ` Jörn Engel
2003-06-12 8:09 ` Arjan van de Ven [this message]
2003-06-12 18:46 ` Aschwin Marsman
2003-06-12 8:17 ` jw schultz
2003-06-11 4:39 ` Lucas Correia Villa Real
2003-06-12 22:23 ` Jerome Chantelauze
2003-06-13 9:31 ` Alan Cox
2003-06-12 8:59 John Bradford
2003-06-12 16:30 ` iain d broadfoot
2003-06-13 11:29 ` Stephan von Krawczynski
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=1055405396.5785.1.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=Michael.Knigge@set-software.de \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®