From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([184.105.139.130]:47034 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932534AbeCSXem (ORCPT ); Mon, 19 Mar 2018 19:34:42 -0400 Date: Mon, 19 Mar 2018 19:34:40 -0400 (EDT) Message-Id: <20180319.193440.1570733225238398675.davem@davemloft.net> To: swise@opengridcomputing.com Cc: rajur@chelsio.com, dledford@redhat.com, linux-rdma@vger.kernel.org, jgg@ziepe.ca, netdev@vger.kernel.org, bharat@chelsio.com, ganeshgr@chelsio.com, rahul.lakkireddy@chelsio.com Subject: Re: interdependencies with cxgb4 and iw_cxgb4 From: David Miller In-Reply-To: <2cbb87bf-9020-2788-be75-1dd7f48f6c42@opengridcomputing.com> References: <022f01d3bba9$82e94870$88bbd950$@opengridcomputing.com> <20180316.122150.516267509367905206.davem@davemloft.net> <2cbb87bf-9020-2788-be75-1dd7f48f6c42@opengridcomputing.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT 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.