From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leon Romanovsky Subject: Re: iproute2 net-next Date: Tue, 26 Dec 2017 11:35:47 +0200 Message-ID: <20171226093547.GC10734@mtr-leonro.local> References: <20171225104919.2568e975@xeon-e3> <20171226044743.GK2942@mtr-leonro.local> <20171225221426.57d4af0b@xeon-e3> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w7PDEPdKQumQfZlR" Cc: netdev@vger.kernel.org To: Stephen Hemminger Return-path: Received: from mail.kernel.org ([198.145.29.99]:34072 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705AbdLZJfv (ORCPT ); Tue, 26 Dec 2017 04:35:51 -0500 Content-Disposition: inline In-Reply-To: <20171225221426.57d4af0b@xeon-e3> Sender: netdev-owner@vger.kernel.org List-ID: --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Dec 25, 2017 at 10:14:26PM -0800, Stephen Hemminger wrote: > On Tue, 26 Dec 2017 06:47:43 +0200 > Leon Romanovsky wrote: > > > On Mon, Dec 25, 2017 at 10:49:19AM -0800, Stephen Hemminger wrote: > > > David Ahern has agreed to take over managing the net-next branch of iproute2. > > > The new location is: > > > https://git.kernel.org/pub/scm/linux/kernel/git/dsahern/iproute2-next.git/ > > > > > > In the past, I have accepted new features into iproute2 master branch, but > > > am changing the policy so that outside of the merge window (up until -rc1) > > > new features will get put into net-next to get some more review and testing > > > time. This means that things like the proposed batch streaming mode will > > > go through net-next. > > > > > > > Hi Stephen, > > > > Did you consider to create one shared repo for the iproute2 to allow > > multiple committers workflow? > > For now having separate trees is best, there is no need for multiple > committers the load is very light. > > > > It will be much convenient for the users to have one place for > > master/stable/net-next branches, instead of actually following two > > different repositories. > > If you are doing network development, you already need to deal with > multiple repo's on the kernel side so there is no difference. I agree with you that one extra "git remote add .." is not so huge and all people who develop for the netdev will do it. My concern is about Documentation and newcomers, who will have a hard time to find a right tree. Thanks > > > > > Example, of such shared repo: > > BPF: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/ > > Bluetooth: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/ > > RDMA: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/ > > Most of these are high volume or vendor silo'd which is not the case here. > --w7PDEPdKQumQfZlR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkhr/r4Op1/04yqaB5GN7iDZyWKcFAlpCF/MACgkQ5GN7iDZy WKdoxg//cx0MCWfY0ZNkCTfgTGBcaVl9B/Y5Zyea/dhOsYi3TJWZVNZ2XaJFeU9y OUSgp2yyLdvIfw8juOkCQ/KS2ZPsHhvxGbfEYH2tr2fxj+WjQ+0ZOlRtfXjoxECz k2KEcq0H04ShKF+RcZuT7/xQolwHe1a7wue1AfiCaIsAzFTb4C3dX81srD30i4Bi wzd9JFhX/6ohxTL+iKRb9Z627fV6TSAIppK40dZlpq4h7z/Dm+cs1qACIGssKUPp Gr+/qxMSw5gX2wLn8yExvcPQCFFOCNW6HsiWAFPVB+vEqZ6V4T5wXkROU0FnN8tU zSAx3trOSzNRkbEpfduqwRq4N1VX7XoXZq/9HmSzyO2+kLvBPIM/y4BQjzBNhQEB AzbABYVvayTN91OH3d2GYJ/TWKBZ+YsPGrzkqCKlEx3jMo79yxsqrF6Qo2lPmVFm hxo9DFfh4hjvuTB7WK+ghgM9rGmqOB+py55qmk6klNDSes3Kog4gjW8Bivhhy9EB wWmM94+nnRp3Ygy1jFePiv4LP+jJsS9rKB5hfqAOo6DmCN0cpiZFMWuNOClR7FTF N4Yh9SU0AY5bORGpSt90AdcpPa1RVl9KVmINzbxVCP69HKBbe91lmqD64NKSeB+5 Okb5aFc8V07aBq6RW50SVmPHhcXwzOpF2U1Tm5BVYAnsoiRoDXU= =NtG1 -----END PGP SIGNATURE----- --w7PDEPdKQumQfZlR--