linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@gmail.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org, axboe@suse.de,
	herbert@gondor.apana.org.au, michael.madore@gmail.com,
	david-b@pacbell.net, gregkh@suse.de, paulmck@us.ibm.com,
	gohai@gmx.net, luca.risolia@studio.unibo.it, p_christ@hol.gr
Subject: Re: 2.6.15-rc6: known regressions in the kernel Bugzilla
Date: Fri, 23 Dec 2005 12:32:59 -0500	[thread overview]
Message-ID: <37219a840512230932m5c371f80gbde4cf652bbd1728@mail.gmail.com> (raw)
In-Reply-To: <43AC1791.1080806@tmr.com>

On 12/23/05, Bill Davidsen <davidsen@tmr.com> wrote:
> Andrew Morton wrote:
> > Adrian Bunk <bunk@stusta.de> wrote:
> >
> >>not a post-2.6.14 regression
> >>
> >
> >
> > Well yeah.  But that doesn't mean thse things have lower priority that
> > post-2.6.14 regressions.
> >
> > I understand what you're doing here, but we should in general concentrate
> > upon the most severe bugs rather than upon the most recent..
>
> Hypocratic oath: "First, do no harm."
>
> If a new kernel version can't make things *better*, at least it
> shouldn't make them *worse*. New features are good, performance
> improvements are good, breaking working systems with an update is not good.
>
> I'm with Adrian on this, if you want people to test and report with -rc
> kernels, then there should be some urgency to addressing the reported
> problems.

I agree.  Quite frankly, I am extremely surprised that this matter is
even up for discussion.  Is it really so important to release 2.6.15
before the end of 2005 that we dont even have the time to fix
regressions that have already been reported in older kernels? 
ESPECIALLY given that patches are said to be available?

IMHO, I agree that new regressions are most important to fix, but I
feel that old regressions are extremely important to fix as well.  If
we know of more regressions that CAN be fixed before a kernel release,
why not do it?

Why should there be any rush to release the next mainline version?  To
make it in time for Christmas?  A better Christmas gift to the world
would be a new release without regressions, be it a month late, who
cares?  (I know -- not likely, but at least we should try)

...and that's my opinion.

-Michael Krufky

  reply	other threads:[~2005-12-23 17:33 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19  0:47 Linux 2.6.15-rc6 Linus Torvalds
2005-12-19  1:30 ` Diego Calleja
2005-12-19  5:41   ` Willy Tarreau
2005-12-20 13:18 ` 2.6.15-rc6: boot failure in saa7134-alsa.c Adrian Bunk
2005-12-20 15:52   ` [Alsa-devel] " Sergey Vlasov
2005-12-20 18:24     ` Linus Torvalds
     [not found]       ` <20051220183455.GC19797@master.mivlgu.local>
2005-12-20 18:57         ` Linus Torvalds
2005-12-20 19:14       ` Adrian Bunk
2005-12-20 19:23         ` Mauro Carvalho Chehab
2005-12-20 19:59         ` Linus Torvalds
2005-12-20 20:23           ` Adrian Bunk
2005-12-20 20:41             ` Linus Torvalds
2005-12-20 20:47               ` James Courtier-Dutton
2005-12-20 21:06                 ` Linus Torvalds
2005-12-20 21:13                 ` [RFC: 2.6 patch] Makefile: sound/ must come before drivers/ Adrian Bunk
2005-12-20 21:24                   ` [Alsa-devel] " Jaroslav Kysela
2005-12-20 22:09                   ` Linus Torvalds
2005-12-21 14:21                     ` Takashi Iwai
2005-12-21 20:49                       ` Mauro Carvalho Chehab
2005-12-22 15:32                         ` Takashi Iwai
2005-12-22 16:06                           ` Mauro Carvalho Chehab
2005-12-22 16:17                             ` Takashi Iwai
2005-12-22 16:38                               ` Mauro Carvalho Chehab
2005-12-21 14:23             ` [Alsa-devel] 2.6.15-rc6: boot failure in saa7134-alsa.c Takashi Iwai
2005-12-21 18:22               ` Adrian Bunk
2005-12-21 18:38                 ` Takashi Iwai
2005-12-21 22:40                   ` Adrian Bunk
2005-12-22 11:39                     ` Takashi Iwai
2005-12-20 20:35           ` James Courtier-Dutton
2005-12-20 21:03             ` Linus Torvalds
2005-12-20 22:17               ` Lee Revell
2005-12-21  1:29                 ` Linus Torvalds
2005-12-21 13:29                 ` Stephen Clark
2005-12-21 14:39               ` Takashi Iwai
2005-12-21 18:32                 ` Linus Torvalds
2005-12-21 18:52                   ` Takashi Iwai
2005-12-21 22:42                     ` Adrian Bunk
2005-12-21 22:50                     ` R C
2005-12-21 16:58               ` Steve deRosier
2005-12-21 18:32                 ` Linus Torvalds
2005-12-21 18:41                   ` Takashi Iwai
2005-12-20 20:35         ` Mauro Carvalho Chehab
2005-12-22  0:59           ` Adrian Bunk
2005-12-22 11:15             ` Mauro Carvalho Chehab
2005-12-22  1:13 ` 2.6.15-rc6: known regressions in the kernel Bugzilla Adrian Bunk
2005-12-22  7:15   ` Greg KH
2005-12-22 12:04     ` Takashi Iwai
2005-12-29 13:23       ` Adrian Bunk
2005-12-30 19:31         ` Lee Revell
2005-12-22  8:52   ` Andrew Morton
2005-12-22 13:57     ` Adrian Bunk
2005-12-22 14:08       ` Andrew Morton
2005-12-22 23:12         ` Adrian Bunk
2005-12-23 15:28         ` Bill Davidsen
2005-12-23 17:32           ` Michael Krufky [this message]
2005-12-24  3:54             ` Andrew Morton
2005-12-25 20:25               ` Bill Davidsen
2005-12-26  1:59               ` Michael Krufky
2005-12-26  2:21               ` Lee Revell
2005-12-22 17:11       ` Brice Goglin
     [not found]       ` <200512222152.05427.p_christ@hol.gr>
     [not found]         ` <1135291436.14685.7.camel@localhost>
2005-12-22 22:55           ` Mike Krufky
     [not found]             ` <200512230121.48882.p_christ@hol.gr>
2005-12-23  1:07               ` Michael Krufky
2005-12-23 11:50       ` Gottfried Haider
2006-01-02 16:00         ` Adrian Bunk
2006-01-04 16:38           ` Greg KH
2005-12-22 15:16     ` David S. Miller

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=37219a840512230932m5c371f80gbde4cf652bbd1728@mail.gmail.com \
    --to=mkrufky@gmail.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=david-b@pacbell.net \
    --cc=davidsen@tmr.com \
    --cc=gohai@gmx.net \
    --cc=gregkh@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.risolia@studio.unibo.it \
    --cc=michael.madore@gmail.com \
    --cc=p_christ@hol.gr \
    --cc=paulmck@us.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).