Date: Sat, 3 Dec 2005 18:09:35 -0500
From: Dave Jones <davej@redhat.com>
To: linux-kernel@vger.kernel.org, Lars Marowsky-Bree <lmb@suse.de>
Subject: Re: RFC: Starting a stable kernel series off the 2.6 kernel
Message-ID: <20051203230935.GD25015@redhat.com>
Mail-Followup-To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, Lars Marowsky-Bree <lmb@suse.de>
References: <20051203135608.GJ31395@stusta.de> <20051203205911.GX18919@marowsky-bree.de> <20051203211329.GC25015@redhat.com> <20051203230254.GI25722@merlin.emma.line.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051203230254.GI25722@merlin.emma.line.org>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1110
Lines: 23

On Sun, Dec 04, 2005 at 12:02:54AM +0100, Matthias Andree wrote:
 > On Sat, 03 Dec 2005, Dave Jones wrote:
 > 
 > > In many cases, submitters of changes know that things are going
 > > to break. Maybe we need a policy that says changes requiring userspace updates
 > > need to be clearly documented in the mails Linus gets (Especially if its
 > > a git pull request), so that when the next point release gets released,
 > > Linus can put a section in the announcement detailing what bits
 > > of userspace are needed to be updated.
 > 
 > This isn't acceptable in stable kernels. FreeBSD has a very tight
 > policy, newer kernels off the same branch support older user space.

The BSDs have an advantage in that their userspace & kernels are closely
coupled. When kernel changes need a userspace change, it gets done at the
same time in the same repository.

		Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/