From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932909AbcIGGrI (ORCPT ); Wed, 7 Sep 2016 02:47:08 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:45251 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932263AbcIGGrG (ORCPT ); Wed, 7 Sep 2016 02:47:06 -0400 X-Sasl-enc: tG0+b6oesHKrpCQw5kgvoJo4QB5DZw/argn930xCQIId 1473230824 Date: Wed, 7 Sep 2016 08:47:12 +0200 From: Greg KH To: Stephen Hemminger Cc: KY Srinivasan , Stephen Rothwell , Arnd Bergmann , David Miller , Networking , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Vitaly Kuznetsov Subject: Re: linux-next: manual merge of the char-misc tree with the net-next tree Message-ID: <20160907064712.GB31273@kroah.com> References: <20160905165650.180e6c89@canb.auug.org.au> <20160905113353.GB27586@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 06, 2016 at 04:07:17PM +0000, Stephen Hemminger wrote: > How about I setup a git tree (hyperv-next) to premerge these. > > We are getting changes from multiple submitters through multiple trees now. That's because there are multiple drivers in different subsystems, so having a single git tree would have to cross multiple subsystem, making merges a mess. Also, I didn't want a git tree as I've still found problems with hyperv patches in the near past, so don't quite trust that they go in without review :( thanks, greg k-h