From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753352Ab0IXIyW (ORCPT ); Fri, 24 Sep 2010 04:54:22 -0400 Received: from lo.gmane.org ([80.91.229.12]:52649 "EHLO lo.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751758Ab0IXIyV (ORCPT ); Fri, 24 Sep 2010 04:54:21 -0400 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: el es Subject: Re: Long maintenance kernel versions. Date: Fri, 24 Sep 2010 08:54:10 +0000 (UTC) Message-ID: References: <20100924053648.GA5453@cr0.nay.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 217.36.116.105 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Geoffrey Said 2x.com> writes: 1. You are top-posting. 2. To my non-developer naked eye it rather looks like - one of the developers steps up and announces he's going to care for this particular kernel version, and how long. 3. If it works and is adopted for your needs, why move ? Stick to it. Test new kernels (apply your patches to them and test with your programs). Nobody knows what you need, unless you tell them - or publish your patches. 4. If you did that, you may publicly maintain the version you have selected for as long as you need. That would be some way to GPL compliance too (IANAL). Move to another kernel version only if it has a new feature that you actually need, as bugfixes usually apply without need to change versions. 5. If more people like what you were doing, you may even become this stable version maintainer. Lukasz