From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from linode.aoot.com ([69.164.194.13]:56654 "EHLO linode.aoot.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753725AbeCTNrG (ORCPT ); Tue, 20 Mar 2018 09:47:06 -0400 From: "Steve Wise" To: "'David Miller'" Cc: , , , , , , , References: <022f01d3bba9$82e94870$88bbd950$@opengridcomputing.com> <20180316.122150.516267509367905206.davem@davemloft.net> <2cbb87bf-9020-2788-be75-1dd7f48f6c42@opengridcomputing.com> <20180319.193440.1570733225238398675.davem@davemloft.net> In-Reply-To: <20180319.193440.1570733225238398675.davem@davemloft.net> Subject: RE: interdependencies with cxgb4 and iw_cxgb4 Date: Tue, 20 Mar 2018 08:47:04 -0500 Message-ID: <01a201d3c051$eebbded0$cc339c70$@opengridcomputing.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Language: en-us Sender: netdev-owner@vger.kernel.org List-ID: > From: Steve Wise > Date: Mon, 19 Mar 2018 14:50:57 -0500 > > > Let me ask a dumb question:� Why cannot one of the maintaners pull the > > commit from the other mainainer's git repo directly?� IE why have this > > third trusted/signed git repo that has to be on k.o, from which both > > maintainers pull?� If one of you can pull it in via a patch series, > > like you do for all other patches, and then notify the other > > maintainer to pull it from the first maintainers' repo if the series > > meets the requirements that it needs to be in both maintainers' > > repositories?� This avoids adding more staging git repos on k.o.� But > > probably I'm missing something... > > Tree A may not want all of tree B's changes, and vice versa. I was thinking the special commit would go into a branch that was based on, say rc1 or rc2 of one of the maintainers. Then both maintainers pull that into their -next branch. Would that work?