From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, stable-review@kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
stable@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [stable] [0/9] 2.6.31.12-stable review
Date: Sun, 17 Jan 2010 18:30:43 +0200 [thread overview]
Message-ID: <4B533B33.5030800@pardus.org.tr> (raw)
In-Reply-To: <20100117161853.GA31781@kroah.com>
Greg KH wrote:
>> Personally I really don't like the idea of "all users should really be
>> moving to .3x" which is true for individual bleeding edge users which
>> compiles and uses their own kernel but there are still distributions
>> around (as well as the one that I'm trying to maintain the kernel
>> part) which ships 2.6.31.
>
> Distros can easily add additional patches to their kernel if they wish
> to keep the .31 kernel alive longer. I am only one person, and can not
> maintain 3 different kernel trees and remain sane.
Yep I know, that's what I'm doing, I just want to make people aware of the problems. I somehow feel a little
bit guilty if I don't report some problems that I've spotted as downstream.
You're totally right, the maintenance of 1 kernel tree would be enough messy and time-consuming, I can't
even think about 3 trees..
>
> You aren't the first to think that .31 would be a "long term" kernel. I
> have never stated this, and I wonder where that rumor came from.
Well I thought that .29 would be that lucky one, and .30, and .31. Not something that I
heard from anyone :)
>
> Yes, I will be maintaining the .32 kernel in a "long-term" manner. I
> have mentioned it before to a number of people, but don't know if I've
> done any "official" announcement. Things get lost in the lkml volume at
> times.
That's nice to hear about that.
>
> Ok, to help you solve this issue, I will be willing to do one more .31
> release after this one. Just send me the git commit ids of the patches
> you wish for me to include, and I will do so.
>
> Sound good?
No that's not necessary at all. I didn't write that to push you for another release.
I just wanted to share my ideas and got reasonable answers from you.
Thanks again.
Ozan
next prev parent reply other threads:[~2010-01-17 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 22:48 [0/9] 2.6.31.12-stable review Greg KH
2010-01-14 22:46 ` [1/9] fasync: split fasync_helper() into separate add/remove functions Greg KH
2010-01-14 22:46 ` [2/9] hwmon: (adt7462) Fix pin 28 monitoring Greg KH
2010-01-14 22:46 ` [3/9] kernel/signal.c: fix kernel information leak with print-fatal-signals=1 Greg KH
2010-01-14 22:46 ` [4/9] netfilter: ebtables: enforce CAP_NET_ADMIN Greg KH
2010-01-14 22:46 ` [5/9] netfilter: nf_ct_ftp: fix out of bounds read in update_nl_seq() Greg KH
2010-01-14 22:46 ` [6/9] quota: Fix dquot_transfer for filesystems different from ext4 Greg KH
2010-01-14 22:46 ` [7/9] fix braindamage in audit_tree.c untag_chunk() Greg KH
2010-01-14 22:46 ` [8/9] fix more leaks in audit_tree.c tag_chunk() Greg KH
2010-01-14 22:46 ` [9/9] ipv6: skb_dst() can be NULL in ipv6_hop_jumbo() Greg KH
2010-01-16 19:03 ` [0/9] 2.6.31.12-stable review Ozan Çağlayan
2010-01-16 19:07 ` H. Peter Anvin
2010-01-17 3:23 ` [stable] " Greg KH
2010-01-17 16:07 ` Ozan Çağlayan
2010-01-17 16:18 ` Greg KH
2010-01-17 16:30 ` Ozan Çağlayan [this message]
2010-01-17 18:02 ` Henrique de Moraes Holschuh
2010-01-18 5:42 ` Greg KH
2010-01-18 7:49 ` [Stable-review] " Nikola Ciprich
2010-01-19 4:07 ` [stable] [Stable-review] " Greg KH
2010-01-19 23:02 ` [stable] " Greg KH
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=4B533B33.5030800@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@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).