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 D54CA94C for ; Fri, 15 Jul 2016 11:42:29 +0000 (UTC) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 42ABF1E6 for ; Fri, 15 Jul 2016 11:42:29 +0000 (UTC) Date: Fri, 15 Jul 2016 20:42:14 +0900 From: Greg KH To: Jiri Kosina Message-ID: <20160715114214.GB27936@kroah.com> References: <20160714031753.GA28722@kroah.com> <20160714100603.GJ9976@sirena.org.uk> <20160715002239.GA31603@kroah.com> <5788337F.8000500@roeck-us.net> <20160715014103.GA5791@kroah.com> <578850EB.3090109@roeck-us.net> <20160715042938.GA5527@kroah.com> <874m7rcus8.fsf@notabene.neil.brown.name> <20160715061424.GA16223@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: James Bottomley , Trond Myklebust , "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel unit testing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Jul 15, 2016 at 09:02:19AM +0200, Jiri Kosina wrote: > On Fri, 15 Jul 2016, Greg KH wrote: > > > > > during new releases they use quilt for all of their work, adding and > > > > removing and updating patches all the time. > > > > > > So you are saying quilt is good for release management, and Guenter is > > > saying it is bad for development. Maybe you are in agreement. > > > > Heh, yes, I think we are in agreement. The "fun" thing is, people take > > the thing you release and do development on it. So the developers want > > the output of your release in a format that they can do work with. > > > > I talked with Geert today about this, and he gave me some ideas for how > > to make the output of the LTSI tree in a git tree that people can work > > off of. Much like I've started to do now with the stable trees, and the > > -rc git tree of patches built from my quilt series. I'll work on this > > over time and see how that goes. > > FWIW what we do in SUSE is that we actually have our kernels maintained as > a quilt series (in git), but at the same time we are actually > automatically generating proper non-rebasing git tree from that series, so > that our partners can work on a proper git tree. I think it's a rather > successful model. > > If you'd like to see this in practice, then this is how the "primary" tree > (to which developers are actually pushing patches backported from > upstream) looks like: > > http://kernel.suse.com/cgit/kernel-source/tree/?h=SLE12-SP2 > http://kernel.suse.com/cgit/kernel-source/log/?h=SLE12-SP2 > > and this is how the auto-generated proper git tree looks like > > http://kernel.suse.com/cgit/kernel/tree/?h=SLE12-SP2 > http://kernel.suse.com/cgit/kernel/tree/?h=SLE12-SP2 Nice, I didn't know about these. But how do you deal with patches in the middle of the series that get changed, when you rebuild the git branch? Or do you have a lot of different branches? Any pointer to some workflow documentation that you might have for how this all works? thanks, greg k-h