[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1307152319490.16723@nftneq.ynat.uz>
Date: Mon, 15 Jul 2013 23:24:52 -0700 (PDT)
From: David Lang <david@...g.hm>
To: Greg KH <greg@...ah.com>
cc: James Bottomley <James.Bottomley@...senPartnership.com>,
ksummit-2013-discuss@...ts.linuxfoundation.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: KS Topic request: Handling the Stable kernel, let's dump the
cc: stable tag
On Mon, 15 Jul 2013, Greg KH wrote:
> I don't like this at all, just for the simple reason that it will push
> the majority of the work of stable kernel development on to the
> subsystem maintainers, who have enough work to do as it is.
>
> Stable tree stuff should cause almost _no_ extra burden on the kernel
> developers, because it is something that I, and a few other people, have
> agreed to do with our time. It has taken me 8 _years_ to finally get
> maintainers to agree to mark stuff for the stable tree, and fine-tune a
> development process that makes it easy for us to do this backport work.
It's important to remember that the subsystem maintainers have essentially no
input on how many stable trees there are or how long they are maintained.
That is entirely up to the people maintaining the stable trees.
Just because some crazy person ;-) decides to maintain 2.4 for many years
doesn't mean that every subsystem maintainer needs to worry about backporting
patches from 3.11 all the way back to 2.4. The fact that they are as willing as
they are to review the results of the backports for problems in amazing.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists