From: Stephen Hemminger <stephen@networkplumber.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 net-next
Date: Mon, 25 Dec 2017 22:14:26 -0800 [thread overview]
Message-ID: <20171225221426.57d4af0b@xeon-e3> (raw)
In-Reply-To: <20171226044743.GK2942@mtr-leonro.local>
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
On Tue, 26 Dec 2017 06:47:43 +0200
Leon Romanovsky <leon@kernel.org> 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.
>
> 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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-26 6:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 18:49 iproute2 net-next Stephen Hemminger
2017-12-26 4:47 ` Leon Romanovsky
2017-12-26 6:14 ` Stephen Hemminger [this message]
2017-12-26 9:35 ` Leon Romanovsky
2017-12-28 23:46 ` Daniel Borkmann
2017-12-29 8:58 ` Jiri Pirko
2017-12-30 4:00 ` Stephen Hemminger
2017-12-30 20:24 ` Daniel Borkmann
2018-01-16 1:56 ` Marcelo Ricardo Leitner
2018-01-16 2:59 ` David Ahern
2018-01-16 3:29 ` Jakub Kicinski
2018-01-16 19:06 ` David Ahern
2018-01-22 16:07 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171225221426.57d4af0b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.