From: Andi Kleen <ak@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc7: known regressions
Date: Mon, 2 Jan 2006 18:38:37 +0100 [thread overview]
Message-ID: <200601021838.38310.ak@suse.de> (raw)
In-Reply-To: <20060102172340.GI17398@stusta.de>
On Monday 02 January 2006 18:23, Adrian Bunk wrote:
> Would you veto against a section "known regressions" in the final 2.6.15
> announcement listing this issue with a link to the Bugzilla bug?
Yes for this case. The original was likely so fragile that it might
break only with minor changes in the hardware configuration.
In general listing known regressions is a good idea though.
It might be a good idea to give them different priorities though - e.g.
a broken BIOS with a missing workaround is less priority than
a pure Linux bug.
-Andi
next prev parent reply other threads:[~2006-01-02 17:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 3:39 Ho ho ho.. Linux 2.6.15-rc7 Linus Torvalds
2005-12-25 5:00 ` Keith Owens
2005-12-26 5:23 ` Grant Coady
2005-12-26 13:54 ` Kalin KOZHUHAROV
2005-12-28 9:11 ` Paul Rolland
2005-12-26 18:02 ` Mark Knecht
2005-12-26 18:14 ` Lee Revell
2005-12-27 2:49 ` Mark Knecht
2005-12-27 5:56 ` Michael Krufky
2005-12-27 13:23 ` James Courtier-Dutton
2005-12-27 17:53 ` Michael Krufky
2005-12-26 18:50 ` Markus Koßmann
2005-12-26 23:24 ` Mauro Carvalho Chehab
2005-12-27 5:47 ` Michael Krufky
2005-12-27 12:43 ` Pekka Enberg
2005-12-29 13:39 ` [2.6.15-rc7 patch] Reject SRAT tables that don't cover all memory Adrian Bunk
2005-12-29 16:07 ` Andi Kleen
2005-12-29 16:20 ` Adrian Bunk
2005-12-29 16:23 ` Andi Kleen
2006-01-02 16:46 ` 2.6.15-rc7: known regressions Adrian Bunk
2006-01-02 17:07 ` Andi Kleen
2006-01-02 17:23 ` Adrian Bunk
2006-01-02 17:38 ` Andi Kleen [this message]
2006-01-02 18:30 ` Ochal Christophe
2006-01-02 18:57 ` Paul E. McKenney
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=200601021838.38310.ak@suse.de \
--to=ak@suse.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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