From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: iproute2 net-next Date: Mon, 25 Dec 2017 22:14:26 -0800 Message-ID: <20171225221426.57d4af0b@xeon-e3> References: <20171225104919.2568e975@xeon-e3> <20171226044743.GK2942@mtr-leonro.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Ge1V1lHCNH=OpdVGv+D6s5D"; protocol="application/pgp-signature" Cc: netdev@vger.kernel.org To: Leon Romanovsky Return-path: Received: from mail-pf0-f169.google.com ([209.85.192.169]:39218 "EHLO mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705AbdLZGOa (ORCPT ); Tue, 26 Dec 2017 01:14:30 -0500 Received: by mail-pf0-f169.google.com with SMTP id l24so18426167pfj.6 for ; Mon, 25 Dec 2017 22:14:30 -0800 (PST) In-Reply-To: <20171226044743.GK2942@mtr-leonro.local> Sender: netdev-owner@vger.kernel.org List-ID: --Sig_/Ge1V1lHCNH=OpdVGv+D6s5D Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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 ipr= oute2. > > 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 -r= c1) > > new features will get put into net-next to get some more review and tes= ting > > time. This means that things like the proposed batch streaming mode will > > go through net-next. > > =20 >=20 > Hi Stephen, >=20 > 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. >=20 > 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/blue= tooth-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. --Sig_/Ge1V1lHCNH=OpdVGv+D6s5D Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEn2/DRbBb5+dmuDyPgKd/YJXN5H4FAlpB6MIACgkQgKd/YJXN 5H5PbhAArndZp2CoynmOTZAUbC8SqEQU9aJitCud/PfeqRDJuPjOxz3ZRnAOBkBP SPTmrIIkwwqbtI8qFC3//SxqYXZKjAxRyBZrgqu+UBpL4A0swMvhcW1iz4M6+vBs Z5sAyrdz23Nh/kNKLiib5N1ov0F1mOHiOsgdGetvsonBsxmiqs4y5XXmVE8meHw/ MaPKm7CCN2Pe6EFnwIXkSd/c5si3c+oJu0AyoNWajrWsmRryddcIISHiyskYPtf8 zhCUq4KzRqcHYwz/kubPXi6PmK8JraIQVI/Ba4jA288t3nmXfW6TVZB6XqCzx4os 3hHj00A6TZkcJvOwOpYegFgTE+0UWL1J2pLHSXYNBPfqn+VRn3coDdMTeq7Bk9O2 pAYFwIF36aSUudWiWAvYD9WaXRU8uOaTdo9j7xu2EmpUYwaZArL2bNxU58ejtbPC B+mhQeHcDweNcRoiOiEHMF5wujQvT9by0m5OWaG/aKh3WuK6b8zeI5B5PXIwlcx9 PNff7mZ+2+DRXRp8TdtVhULWC5Z/+dHxhaZCOCHICMzCc12hacH5VF3CBK4a3AZc xsKo7xv9hX7/r15m49BGw/47IOc6mNaAhzWOwTq3r+jdKIWKE+o+39r6MjCNo9Rf KKtXqdvdx8AKq4LHMktpTwp9XFjZsYullXt8zDdbHOt2psR4iG0= =GyKk -----END PGP SIGNATURE----- --Sig_/Ge1V1lHCNH=OpdVGv+D6s5D--