From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932523Ab3GKNzo (ORCPT ); Thu, 11 Jul 2013 09:55:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:30313 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755025Ab3GKNzl (ORCPT ); Thu, 11 Jul 2013 09:55:41 -0400 Date: Thu, 11 Jul 2013 14:55:22 +0100 From: Alasdair G Kergon To: Stephen Rothwell Cc: Alasdair G Kergon , Yann Droneaud , Mike Snitzer , Robin Dong , linux-kernel@vger.kernel.org, Jim Ramsay , dm-devel@redhat.com, Mikulas Patocka , "Jun'ichi Nomura" , Rob Herring , Linus Torvalds , Milan Broz , Guenter Roeck Subject: Re: [dm-devel] [git pull] device-mapper changes for 3.11 Message-ID: <20130711135522.GN8530@agk-dp.fab.redhat.com> Mail-Followup-To: Stephen Rothwell , Alasdair G Kergon , Yann Droneaud , Mike Snitzer , Robin Dong , linux-kernel@vger.kernel.org, Jim Ramsay , dm-devel@redhat.com, Mikulas Patocka , Jun'ichi Nomura , Rob Herring , Linus Torvalds , Milan Broz , Guenter Roeck References: <20130711013448.GD32399@agk-dp.fab.redhat.com> <20130711162040.8a82cb97a6c647c4f61f919b@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130711162040.8a82cb97a6c647c4f61f919b@canb.auug.org.au> Organization: Red Hat UK Ltd. Registered in England and Wales, number 03798903. Registered Office: 64 Baker Street, 4th floor, London, W1U 7DF. User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 11, 2013 at 04:20:40PM +1000, Stephen Rothwell wrote: > Alistair, is there some reason that you cannot maintain some relatively > stable git tree for me to fetch (instead of the quilt series). Well Mike Snitzer is becoming a joint maintainer and this also requires changes to the workflow so watch this space. > Also, > there is not real reason to keep rebasing this stuff (especially just > before sending it to Linus). Most of the time the patches are decoupled from the rest of the tree and the final linux-next kernel is the same regardless of where the quilt tree is attached. I maintain a single sequence of patches where the ones ready for upstream float up to the top and the linux-next export is a by-product and not the primary output. Anyway, like I say, we'll be changing things during the next couple of cycles and we'll bear your suggestions in mind. Alasdair