From: Willy Tarreau <w@1wt.eu>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Adrian Chadd <adrian@freebsd.org>,
Greg KH <gregkh@linuxfoundation.org>,
Sergio Correia <lists@uece.net>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
alan@lxorguk.ukuu.org.uk,
linux-wireless Mailing List <linux-wireless@vger.kernel.org>,
Sujith Manoharan <c_manoha@qca.qualcomm.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [ 00/78] 3.3.2-stable review
Date: Thu, 12 Apr 2012 23:43:36 +0200 [thread overview]
Message-ID: <20120412214336.GB12807@1wt.eu> (raw)
In-Reply-To: <CAMP44s2M_srvKKaicOpr+TF6hw=dxFMVRwMs2K9E_P_ooPMCXw@mail.gmail.com>
On Fri, Apr 13, 2012 at 12:34:59AM +0300, Felipe Contreras wrote:
> Now what happens when:
>
> - you realize the fix made matters worst, in fact, so worst that the
> whole thing is unusable in some systems
>
> Presumably we are now in the next round of:
>
> - fix upstream
>
> But v.3.3.2 is due Friday, which makes it very likely that the fix
> won't get in. And what did we gain? If you simplify the situation to
> what you explained above, it seems very reasonable, but that's not the
> whole picture.
BTW, if you're so in need for critical fixes, why do you jump to the latest
version ? It's known and accepted that stable versions stabilize over time
with a few random hiccups during their early stage. You could have chosen
3.0 instead which generally holds some fixes that cooked longer before being
merged.
There's a cost at living on the bleeding edge. It's fun and sometimes it
hurts but that should not be that dramatic that you spend so many emails
telling how stable releases should be maintained.
Willy
next prev parent reply other threads:[~2012-04-12 21:44 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120411231102.GA6404@kroah.com>
2012-04-11 23:59 ` [ 00/78] 3.3.2-stable review Sergio Correia
2012-04-12 0:29 ` Greg KH
2012-04-12 0:57 ` Sergio Correia
2012-04-12 1:03 ` Felipe Contreras
2012-04-12 1:13 ` Greg KH
2012-04-12 13:32 ` Felipe Contreras
2012-04-12 14:46 ` Greg KH
2012-04-12 16:49 ` Felipe Contreras
2012-04-12 17:24 ` Adrian Chadd
2012-04-12 18:43 ` Felipe Contreras
2012-04-12 18:56 ` Jonathan Nieder
2012-04-12 21:34 ` Felipe Contreras
2012-04-12 21:43 ` Willy Tarreau [this message]
2012-04-12 20:07 ` Greg KH
2012-04-12 20:52 ` Sven-Haegar Koch
2012-04-13 8:57 ` Stefan Richter
2012-04-13 10:29 ` Felipe Contreras
2012-04-13 13:42 ` Stefan Richter
2012-04-13 14:01 ` Stefan Richter
2012-04-13 22:38 ` Felipe Contreras
2012-04-13 23:05 ` Jonathan Nieder
2012-04-13 23:18 ` Felipe Contreras
2012-04-14 5:44 ` Willy Tarreau
2012-04-14 15:43 ` Felipe Contreras
2012-04-14 16:02 ` Willy Tarreau
2012-04-14 9:10 ` Stefan Richter
2012-04-14 15:52 ` Felipe Contreras
2012-04-14 18:08 ` Stefan Richter
2012-04-14 7:41 ` Stefan Richter
2012-04-14 15:29 ` Felipe Contreras
2012-04-14 15:57 ` Willy Tarreau
2012-04-14 19:33 ` Felipe Contreras
2012-04-14 19:58 ` Willy Tarreau
2012-04-14 17:55 ` Stefan Richter
2012-04-14 19:21 ` Felipe Contreras
2012-04-14 21:21 ` Stefan Richter
2012-04-14 22:09 ` Felipe Contreras
2012-04-14 22:47 ` Stefan Richter
2012-04-14 22:56 ` Felipe Contreras
2012-04-14 23:06 ` Adrian Chadd
2012-04-13 19:08 ` [ath9k-devel] " Peter Stuge
2012-04-13 22:53 ` Felipe Contreras
2012-04-14 6:01 ` Willy Tarreau
2012-04-16 16:27 ` Greg KH
2012-04-16 20:11 ` Felipe Contreras
2012-04-16 20:58 ` Greg KH
2012-04-16 21:18 ` Felipe Contreras
2012-04-16 21:27 ` Greg KH
2012-04-16 21:44 ` Felipe Contreras
2012-04-16 22:34 ` Peter Stuge
2012-04-17 5:24 ` Willy Tarreau
2012-04-16 21:50 ` Felipe Contreras
2012-04-16 21:54 ` Don deJuan
2012-04-16 22:02 ` Don deJuan
2012-04-16 21:39 ` Don deJuan
2012-04-12 18:40 ` Willy Tarreau
2012-04-12 19:05 ` Linus Torvalds
2012-04-12 21:20 ` Felipe Contreras
2012-04-12 21:34 ` Linus Torvalds
2012-04-12 21:44 ` Linus Torvalds
2012-04-12 22:02 ` [ath9k-devel] " Luis R. Rodriguez
2012-04-12 22:04 ` Felipe Contreras
2012-04-12 22:07 ` Linus Torvalds
2012-04-12 22:29 ` Felipe Contreras
2012-04-14 10:47 ` Ingo Molnar
2012-04-14 15:59 ` Felipe Contreras
2012-04-15 6:51 ` Ingo Molnar
2012-04-15 17:15 ` Felipe Contreras
2012-04-15 17:29 ` Willy Tarreau
2012-04-15 17:49 ` Linus Torvalds
2012-04-15 22:12 ` Felipe Contreras
2012-04-16 5:32 ` Ingo Molnar
2012-04-16 20:25 ` Felipe Contreras
2012-04-16 21:08 ` Arend van Spriel
2012-04-16 5:39 ` Willy Tarreau
2012-04-16 6:38 ` Ingo Molnar
2012-04-12 22:12 ` David Miller
2012-04-12 22:58 ` Felipe Contreras
2012-04-13 5:34 ` Willy Tarreau
2012-04-13 10:04 ` Felipe Contreras
2012-04-12 21:39 ` Willy Tarreau
2012-04-12 22:02 ` Jesper Juhl
2012-04-12 19:57 ` Alexander Holler
2012-04-12 20:06 ` Greg KH
2012-04-12 20:30 ` Alexander Holler
2012-04-12 22:31 ` Greg KH
2012-04-12 4:16 ` Heinz Diehl
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=20120412214336.GB12807@1wt.eu \
--to=w@1wt.eu \
--cc=adrian@freebsd.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=c_manoha@qca.qualcomm.com \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lists@uece.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).