From: David Marchand <david.marchand@redhat.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Ali Alnubani <alialnu@nvidia.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Luca Boccassi <bluca@debian.org>,
Kevin Traynor <ktraynor@redhat.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] code.dpdk.org bugfix releases
Date: Tue, 8 Jun 2021 14:09:02 +0200 [thread overview]
Message-ID: <CAJFAV8xk7TBTVJVGgcTL7ZSowSOnCdtPpw1tJEy1J5JMLxsNYg@mail.gmail.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35C6182C@smartserver.smartshare.dk>
On Tue, Jun 8, 2021 at 11:58 AM Morten Brørup <mb@smartsharesystems.com> wrote:
> As a frequent user of code.dpdk.org, I think it would be great.
>
> Thomas, David, Luca and Kevin, do any of you oppose to code.dpdk.org showing both the "dpdk" and the "dpdk-stable" repos merged together as one project, if Ali can do it?
I exchanged with Ali on some details, it does not seem that difficult
to implement.
No objection, it seems less confusing for users.
--
David Marchand
next prev parent reply other threads:[~2021-06-08 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 15:18 [dpdk-dev] code.dpdk.org bugfix releases Morten Brørup
2021-06-03 16:10 ` Thomas Monjalon
2021-06-03 18:15 ` Morten Brørup
2021-06-03 19:18 ` Thomas Monjalon
2021-06-03 19:36 ` Morten Brørup
2021-06-04 8:12 ` Thomas Monjalon
2021-06-04 8:19 ` Morten Brørup
2021-06-04 8:47 ` Thomas Monjalon
2021-06-04 9:14 ` Morten Brørup
2021-06-07 12:49 ` Ali Alnubani
2021-06-08 9:57 ` Morten Brørup
2021-06-08 10:23 ` Thomas Monjalon
2021-06-08 13:42 ` Luca Boccassi
2021-06-08 10:35 ` Kevin Traynor
2021-06-08 12:09 ` David Marchand [this message]
2021-06-04 7:00 ` David Marchand
2021-06-04 7:03 ` Morten Brørup
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=CAJFAV8xk7TBTVJVGgcTL7ZSowSOnCdtPpw1tJEy1J5JMLxsNYg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=mb@smartsharesystems.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 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.