maintainers: remove QoS and pipeline repositories
Checks
Commit Message
The git trees dpdk-next-qos and dpdk-next-pipeline were created
to share the load of patches merging.
It has been decided in the Technical Board that the load is not big
enough to justify keeping these repositories.
The patches for ethdev TM and MTR will be managed in dpdk-next-net.
The sched and meter libraries will be managed in the main tree.
The packet framework will be managed in the main tree as well.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
MAINTAINERS | 15 ++-------------
1 file changed, 2 insertions(+), 13 deletions(-)
Comments
On Wed, Aug 12, 2020 at 11:07:23AM +0200, Thomas Monjalon wrote:
> The git trees dpdk-next-qos and dpdk-next-pipeline were created
> to share the load of patches merging.
> It has been decided in the Technical Board that the load is not big
> enough to justify keeping these repositories.
>
> The patches for ethdev TM and MTR will be managed in dpdk-next-net.
> The sched and meter libraries will be managed in the main tree.
> The packet framework will be managed in the main tree as well.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> MAINTAINERS | 15 ++-------------
> 1 file changed, 2 insertions(+), 13 deletions(-)
>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
12/08/2020 14:36, Bruce Richardson:
> On Wed, Aug 12, 2020 at 11:07:23AM +0200, Thomas Monjalon wrote:
> > The git trees dpdk-next-qos and dpdk-next-pipeline were created
> > to share the load of patches merging.
> > It has been decided in the Technical Board that the load is not big
> > enough to justify keeping these repositories.
> >
> > The patches for ethdev TM and MTR will be managed in dpdk-next-net.
> > The sched and meter libraries will be managed in the main tree.
> > The packet framework will be managed in the main tree as well.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, quickly to avoid breaking CI when guessing git tree.
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, August 12, 2020 2:25 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; david.marchand@redhat.com;
> arybchenko@solarflare.com; Yigit, Ferruh <ferruh.yigit@intel.com>;
> Richardson, Bruce <bruce.richardson@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] maintainers: remove QoS and pipeline
> repositories
>
> 12/08/2020 14:36, Bruce Richardson:
> > On Wed, Aug 12, 2020 at 11:07:23AM +0200, Thomas Monjalon wrote:
> > > The git trees dpdk-next-qos and dpdk-next-pipeline were created
> > > to share the load of patches merging.
> > > It has been decided in the Technical Board that the load is not big
> > > enough to justify keeping these repositories.
> > >
> > > The patches for ethdev TM and MTR will be managed in dpdk-next-net.
> > > The sched and meter libraries will be managed in the main tree.
> > > The packet framework will be managed in the main tree as well.
> > >
> > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> >
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Applied, quickly to avoid breaking CI when guessing git tree.
>
>
I am in vacation reading emails every now and then, just saw this.
I am fine with it, as the only purpose of these trees was to sync-up on large pull requests, which was an infrequent event for these trees.
Thomas, thanks for handling this.
Regards,
Cristian
@@ -61,14 +61,6 @@ Next-eventdev Tree
M: Jerin Jacob <jerinj@marvell.com>
T: git://dpdk.org/next/dpdk-next-eventdev
-Next-qos Tree
-M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
-T: git://dpdk.org/next/dpdk-next-qos
-
-Next-pipeline Tree
-M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
-T: git://dpdk.org/next/dpdk-next-pipeline
-
Stable Branches
M: Luca Boccassi <bluca@debian.org>
M: Kevin Traynor <ktraynor@redhat.com>
@@ -408,12 +400,12 @@ F: lib/librte_ethdev/rte_flow*
Traffic Management API - EXPERIMENTAL
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
-T: git://dpdk.org/next/dpdk-next-qos
+T: git://dpdk.org/next/dpdk-next-net
F: lib/librte_ethdev/rte_tm*
Traffic Metering and Policing API - EXPERIMENTAL
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
-T: git://dpdk.org/next/dpdk-next-qos
+T: git://dpdk.org/next/dpdk-next-net
F: lib/librte_ethdev/rte_mtr*
Baseband API - EXPERIMENTAL
@@ -1331,7 +1323,6 @@ F: doc/guides/sample_app_ug/packet_ordering.rst
Hierarchical scheduler
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
M: Jasvinder Singh <jasvinder.singh@intel.com>
-T: git://dpdk.org/next/dpdk-next-qos
F: lib/librte_sched/
F: doc/guides/prog_guide/qos_framework.rst
F: app/test/test_red.c
@@ -1351,7 +1342,6 @@ F: doc/guides/tools/pdump.rst
Packet Framework
----------------
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
-T: git://dpdk.org/next/dpdk-next-pipeline
F: lib/librte_pipeline/
F: lib/librte_port/
F: lib/librte_table/
@@ -1419,7 +1409,6 @@ F: app/test-fib/
Traffic metering
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
-T: git://dpdk.org/next/dpdk-next-qos
F: lib/librte_meter/
F: doc/guides/sample_app_ug/qos_scheduler.rst
F: app/test/test_meter.c