DPDK patches and discussions
 help / color / mirror / Atom feed
From: Morten Brørup <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>,
	"Ali Alnubani" <alialnu@nvidia.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] code.dpdk.org bugfix releases
Date: Fri, 4 Jun 2021 10:19:56 +0200
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35C61820@smartserver.smartshare.dk> (raw)
In-Reply-To: <6441912.U1qnyMZzFn@thomas>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Friday, 4 June 2021 10.12
> 
> 03/06/2021 21:36, Morten Brørup:
> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > Sent: Thursday, 3 June 2021 21.18
> > k-dev] code.dpdk.org bugfix releases
> > >
> > > 03/06/2021 20:15, Morten Brørup:
> > > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas
> > > Monjalon
> > > > > Sent: Thursday, 3 June 2021 18.11
> > > > >
> > > > > 03/06/2021 17:18, Morten Brørup:
> > > > > > Hi all,
> > > > > >
> > > > > > Bugfix releases are missing on code.dpdk.org.
> > > > > >
> > > > > > E.g. version 17.11 is present, but version 17.11.10 is
> missing.
> > > > > >
> > > > > > Can whoever is the maintainer of code.dpdk.org please fix
> this.
> > > > >
> > > > > Ali is the admin of dpdk.org.
> > > > > I'm not sure your request is easy because stable releases
> > > > > are in a separate repository dpdk-stable.git.
> > > >
> > > > Ali, it would be great if you can include them.
> > > > Not having easy access to browse the source code of the LTS
> > > > bugfix releases could be a barrier for DPDK users to upgrade
> > > > to the latest LTS bugfix release.
> > >
> > > Actually it's already included (thanks Ali for reminding it to me):
> > > 	https://code.dpdk.org/dpdk-stable/v20.11/source
> > >
> > > There are 2 different repos and that's how it is exposed in this
> tool.
> >
> > Great... It was just me not knowing where to click. We learn
> something new every day!
> >
> > > It may be a bit confusing.
> > > Do you think it would be OK to rename dpdk-stable to dpdk in this
> tool?
> >
> > Having learned that the box saying "dpdk" is a dropdown, I headed
> over to my favorite Linux source code browser at Bootlin. And they
> already have what I was asking for:
> https://elixir.bootlin.com/dpdk/latest/source
> >
> > And they call it "dpdk", not "dpdk-stable"... so I support Thomas'
> suggestion here.
> 
> No, what is in bootlin instance is really dpdk, not dpdk-stable.

You are right. I got confused because they also showed the -rc releases.

> 
> > Or alternatively: https://code.dpdk.org/ currently redirects to
> https://code.dpdk.org/dpdk/latest/source. Perhaps it could redirect to
> https://code.dpdk.org/dpdk-stable/latest/source instead.
> >
> > 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.


  reply	other threads:[~2021-06-04  8:20 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 [this message]
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
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=98CBD80474FA8B44BF855DF32C47DC35C61820@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git