From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Ali Alnubani <alialnu@nvidia.com>,
dev@dpdk.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] code.dpdk.org bugfix releases
Date: Fri, 04 Jun 2021 10:47:33 +0200 [thread overview]
Message-ID: <3254349.IzmrIriAmv@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35C61820@smartserver.smartshare.dk>
04/06/2021 10:19, Morten Brørup:
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > > Now, I have another question: What does code.dpdk.org show for "dpdk"
> > that it does not show for "dpdk-stable"?
> >
> > stable releases are only in dpdk-stable but everything is in dpdk-
> > stable.
>
> If you meant "dpdk" (not "dpdk-stable") at the end of that sentence, then "dpdk" at code.dpdk.org should show many more tags, as I originally requested.
No I meant dpdk-stable :)
In DPDK we have base releases,
in dpdk-stable we have the maintained base releases and the minor stable releases.
At the end, we don't have all tags in a single repo.
next prev parent reply other threads:[~2021-06-04 8:47 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 [this message]
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
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=3254349.IzmrIriAmv@thomas \
--to=thomas@monjalon.net \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
/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.