From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Ali Alnubani" <alialnu@nvidia.com>,
"NBU-Contact-Thomas Monjalon" <thomas@monjalon.net>,
<david.marchand@redhat.com>, "Luca Boccassi" <bluca@debian.org>,
"Kevin Traynor" <ktraynor@redhat.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] code.dpdk.org bugfix releases
Date: Tue, 8 Jun 2021 11:57:59 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35C6182C@smartserver.smartshare.dk> (raw)
In-Reply-To: <DM4PR12MB5167C3AB44D32ACF5EABEB0CDA389@DM4PR12MB5167.namprd12.prod.outlook.com>
+ Stable maintainers: Luca Boccassi, Kevin Traynor.
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ali Alnubani
> Sent: Monday, 7 June 2021 14.49
>
> Hi,
>
> > From: Morten Brørup <mb@smartsharesystems.com>
> > Sent: Friday, June 4, 2021 12:14 PM
> >
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas
> Monjalon
> > > Sent: Friday, 4 June 2021 10.48
> > >
> > > 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.
> >
> > OK. Now I get it!
> >
> > Then code.dpdk.org probably works as intended. It was just me being
> > confused about it, because I'm used to a mono-repo world. "It's a
> feature,
> > not a bug."
> >
> > I guess it would be difficult to merge the data from the two repos
> into one
> > big code.dpdk.org source code browser. Which was your first response
> to my
> > original request, Thomas. Ali, what do you think?
>
> I don't think it's too difficult to merge the tags of both repos under
> a single project in code.dpdk.org. Will need to verify though.
> Let me know if you think it's better to do so.
>
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?
-Morten
next prev parent reply other threads:[~2021-06-08 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 15:18 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 [this message]
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=98CBD80474FA8B44BF855DF32C47DC35C6182C@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.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).