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 E2E6AE78 for ; Tue, 18 Sep 2018 15:02:02 +0000 (UTC) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8D6DE7DC for ; Tue, 18 Sep 2018 15:02:02 +0000 (UTC) To: Geert Uytterhoeven From: "Martin K. Petersen" References: <1536142432.8121.6.camel@HansenPartnership.com> <20180905113715.GJ9781@sirena.org.uk> <20180905150315.GA10819@linux.vnet.ibm.com> <20180905115008.22e3d21f@gandalf.local.home> <20180905162007.GO4225@linux.vnet.ibm.com> <1536165914.3627.17.camel@HansenPartnership.com> <1536176428.3627.28.camel@HansenPartnership.com> Date: Tue, 18 Sep 2018 11:01:50 -0400 In-Reply-To: (Geert Uytterhoeven's message of "Tue, 18 Sep 2018 16:12:31 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain Cc: James Bottomley , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] Distribution kernel bugzillas considered harmful List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Geert, > You could start using topic branches (for core, and per driver/vendor), > and recreate your for-next branch as a merge of all topic branches on a > daily basis. If one patch series turns out to be bad, at least the commit > IDs in the other topic branches will remain stable. Yeah. I thought about doing what Jens does, splitting core and drivers into separate branches. However, compared to block I have so few SCSI core updates that I am not convinced it's worth it. Core changes only amount to a couple percent of the total number of commits every release. For topic branches to be truly effective I'd need a separate branch per driver. Not impossible, but it seems like a pretty big hammer... -- Martin K. Petersen Oracle Linux Engineering