From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Vanilla sources stabilization policy change
Date: Thu, 8 Aug 2013 15:29:06 -0700 [thread overview]
Message-ID: <20130808222906.GA30314@kroah.com> (raw)
In-Reply-To: <20130808044309.3af5c4f5@TOMWIJ-GENTOO>
On Thu, Aug 08, 2013 at 04:43:09AM +0200, Tom Wijsman wrote:
> On Wed, 7 Aug 2013 16:19:43 -0700
> Greg KH <gregkh@gentoo.org> wrote:
>
> > On Thu, Aug 08, 2013 at 12:50:32AM +0200, Peter Stuge wrote:
> > > Greg KH wrote:
> > > > See above for why it is not easy at all, and, why even if we do
> > > > know some fixes are security ones, we would not tag them as such
> > > > anyway.
> > >
> > > I think this supports the argument that the better kernel is always
> > > the one with the most fixes.
>
> Define "better"; because 3.10.0 has also been worse than the last 3.9
> release in some ways, despite it having more fixes than the last 3.9.
How was it "worse"? You don't seem to define that either :)
Yes, there are always going to be bugs and regressions, but as long as
we are fixing them more than we are making them, we are doing ok.
greg k-h
next prev parent reply other threads:[~2013-08-08 22:29 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 14:02 [gentoo-dev] Vanilla sources stabilization policy change Mike Pagano
2013-07-24 17:37 ` Peter Stuge
2013-07-24 17:43 ` Alex Xu
2013-07-24 17:46 ` Rich Freeman
2013-07-24 17:54 ` Peter Stuge
2013-07-24 18:25 ` Rich Freeman
2013-07-24 19:01 ` Peter Stuge
2013-07-24 19:10 ` Ben Kohler
2013-07-24 19:15 ` Peter Stuge
2013-07-24 20:40 ` Tom Wijsman
2013-07-24 20:40 ` Rich Freeman
2013-07-24 20:45 ` Ciaran McCreesh
2013-07-24 23:09 ` Greg KH
2013-07-25 1:42 ` Rich Freeman
2013-08-07 9:37 ` Tom Wijsman
2013-08-07 22:44 ` Greg KH
2013-08-07 22:50 ` Peter Stuge
2013-08-07 23:19 ` Greg KH
2013-08-08 2:43 ` Tom Wijsman
2013-08-08 22:29 ` Greg KH [this message]
2013-08-09 8:10 ` Tom Wijsman
2013-08-08 23:44 ` Peter Stuge
2013-08-09 8:23 ` Tom Wijsman
2013-08-08 2:37 ` Tom Wijsman
2013-08-08 22:32 ` Greg KH
2013-08-09 8:34 ` Tom Wijsman
2013-08-09 10:38 ` Rich Freeman
2013-08-09 13:28 ` Tom Wijsman
2013-08-09 19:27 ` Greg KH
2013-08-09 19:30 ` Greg KH
2013-08-09 19:46 ` Tom Wijsman
2013-08-09 19:57 ` Greg KH
2013-07-24 20:22 ` Tom Wijsman
2013-07-24 20:06 ` Tom Wijsman
2013-07-24 17:49 ` Peter Stuge
2013-07-24 17:58 ` Alex Xu
2013-07-24 18:16 ` Peter Stuge
2013-07-24 20:59 ` Tom Wijsman
2013-07-24 22:17 ` Markos Chandras
2013-08-07 9:47 ` Tom Wijsman
2013-07-27 8:02 ` Sergey Popov
2013-07-27 8:56 ` Chí-Thanh Christopher Nguyễn
2013-07-27 13:28 ` Alexander Berntsen
2013-07-27 13:32 ` Manuel Rüger
2013-07-29 21:45 ` Alexander Berntsen
2013-08-07 9:58 ` Tom Wijsman
2013-07-27 18:20 ` Chí-Thanh Christopher Nguyễn
2013-07-27 13:58 ` Rich Freeman
2013-07-27 18:55 ` Mike Pagano
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=20130808222906.GA30314@kroah.com \
--to=gregkh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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