From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E73E38A1 for ; Thu, 29 Jun 2017 20:27:20 +0000 (UTC) Received: from ozlabs.org (ozlabs.org [103.22.144.67]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 40642403 for ; Thu, 29 Jun 2017 20:27:20 +0000 (UTC) Date: Fri, 30 Jun 2017 06:27:17 +1000 From: Stephen Rothwell To: Kees Cook Message-ID: <20170630062717.534b06e9@canb.auug.org.au> In-Reply-To: References: <1498754169.2834.61.camel@HansenPartnership.com> <1498758126.2834.70.camel@HansenPartnership.com> <20170629182044.GP21846@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: James Bottomley , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Kees, On Thu, 29 Jun 2017 13:16:40 -0700 Kees Cook wrote: > > [1] If the solution for this is to merge other -next trees into mine, > I guess I can do that, though it can be very messy if any of them are > forced to make their commits unstable. It also creates headaches, > AIUI, for sfr if my tree suddenly gains a bunch of other trees so it's > not clear where something came from. I don't have a problem with trees in linux-next sharing *commits* - I have problems when they share *patches* that are different commits (that affect files that get changed in other commits). For the "create a new API" case, if you put that in an immutable tree/branch, then other maintainers can merge that branch as they change to use the new API ... Immutable doesn't mean that fixes can't be applied, it just means that the part that has already been merged by some other tree cannot change. I guess it is useful to track who is merging that immutable branch so that they can be informed if relevant changes are added to it. -- Cheers, Stephen Rothwell