From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jikos@kernel.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 467CC950
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Fri, 15 Jul 2016 11:47:37 +0000 (UTC)
Received: from mx2.suse.de (mx2.suse.de [195.135.220.15])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 14B0310E
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Fri, 15 Jul 2016 11:47:36 +0000 (UTC)
Date: Fri, 15 Jul 2016 13:47:32 +0200 (CEST)
From: Jiri Kosina <jikos@kernel.org>
To: Greg KH <greg@kroah.com>
In-Reply-To: <20160715114214.GB27936@kroah.com>
Message-ID: <alpine.LNX.2.00.1607151344020.24757@cbobk.fhfr.pm>
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>
	<alpine.LNX.2.00.1607150853390.24757@cbobk.fhfr.pm>
	<20160715114214.GB27936@kroah.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Trond Myklebust <trondmy@primarydata.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel unit testing
List-Id: <ksummit-discuss.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/ksummit-discuss/>
List-Post: <mailto:ksummit-discuss@lists.linuxfoundation.org>
List-Help: <mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=subscribe>

On Fri, 15 Jul 2016, Greg KH wrote:

> But how do you deal with patches in the middle of the series that get
> changed, 

For each change (even refresh of existing patch in the middle of the 
series), corresponding git commit is created.

As an example how this looks like, here is a "refresh existing patch in 
the middle of the quilt series" commit:

	http://kernel.suse.com/cgit/kernel-source/commit/?h=SLE12-SP2&id=c8ee9b3eab8f58ad16dcb132a2e1e360b5b8cc9a

and this is the resulting autogenerated commit to the "proper" git tree:

	http://kernel.suse.com/cgit/kernel/commit/?h=SLE12-SP2&id=5d9e4d4df7211ac59578aa4cd009c0d2fbafd1eb

> when you rebuild the git branch?  

I am not sure I properly understand what you mean by "rebuild" here, could 
you please elaborate?

> Or do you have a lot of different branches?  

Every supported release (codestream) has it's own branch.

Thanks,

-- 
Jiri Kosina
SUSE Labs