From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"arybchenko@solarflare.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
Date: Wed, 12 Aug 2020 15:49:50 +0000 [thread overview]
Message-ID: <BYAPR11MB29352216952DB2258B78AF42EB420@BYAPR11MB2935.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2274194.41OL3asWA6@thomas>
> -----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
prev parent reply other threads:[~2020-08-12 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 9:07 Thomas Monjalon
2020-08-12 12:36 ` Bruce Richardson
2020-08-12 13:25 ` Thomas Monjalon
2020-08-12 15:49 ` Dumitrescu, Cristian [this message]
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=BYAPR11MB29352216952DB2258B78AF42EB420@BYAPR11MB2935.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).