From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758908AbcIHKVS (ORCPT ); Thu, 8 Sep 2016 06:21:18 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:38248 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758877AbcIHKVP (ORCPT ); Thu, 8 Sep 2016 06:21:15 -0400 X-Sasl-enc: HugFiN9BR7STfmLnBvHpSoN/wM1dWIDDsk1SyxSocuQ5 1473330069 Date: Thu, 8 Sep 2016 12:21:15 +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: <20160908102115.GA22483@kroah.com> References: <20160905165650.180e6c89@canb.auug.org.au> <20160905113353.GB27586@kroah.com> <20160907064712.GB31273@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 Wed, Sep 07, 2016 at 04:51:12PM +0000, Stephen Hemminger wrote: > It isn't so much about the Pull Request, more about having a single pre-merged > location and making sure that everyone is on the same page for testing. I don't understand. If you want to have a git tree, for testing in linux-next, that's fine, but I still need/want patches in email to take things to be merged "properly" on through to Linus for the sections of the hv code that go through me. thanks, greg k-h