DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jill Lovato <jlovato@linuxfoundation.org>
Cc: dpdk-web <web@dpdk.org>,
	Ashley Weltz <aweltz@linuxfoundation.org>,
	"Tu, Lijuan" <lijuan.tu@intel.com>,
	Jonathan Ribas <spychat@gmail.com>,
	Ogawa Yasufumi <yasufum.o@gmail.com>,
	"Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [dpdk-web] Add links to bugs for hosted projects
Date: Thu, 20 May 2021 08:26:34 +0200	[thread overview]
Message-ID: <2029150.Wv0Pz2GlkR@thomas> (raw)
In-Reply-To: <CANA499GzdUurD4OZn2KbVaDGZYsd78AC4vb6cTZfqeD4vthEag@mail.gmail.com>

20/05/2021 00:24, Jill Lovato:
> Hi Thomas,
> 
> This has been updated: https://www.dpdk.org/hosted-projects/

That's perfect, thank you.


> On Wed, May 19, 2021 at 6:53 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> 
> > Please, would it be possible to add a quick link to the open bugs
> > for each hosted project having a Bugzilla section?
> >
> > The link should appear as "Bugs" and be the last one in the list of links
> > in this page: https://www.dpdk.org/hosted-projects/
> >
> > These are the links for each relevant project:
> >
> >         dpdk-burst-replay
> > https://bugs.dpdk.org/buglist.cgi?product=dpdk-burst-replay&resolution=---
> >
> >         DTS
> > https://bugs.dpdk.org/buglist.cgi?product=DTS&resolution=---
> >
> >         SPP
> > https://bugs.dpdk.org/buglist.cgi?product=SPP&resolution=---
> >
> > Thank you




      reply	other threads:[~2021-05-20  6:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 13:53 Thomas Monjalon
2021-05-19 22:24 ` Jill Lovato
2021-05-20  6:26   ` Thomas Monjalon [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=2029150.Wv0Pz2GlkR@thomas \
    --to=thomas@monjalon.net \
    --cc=aweltz@linuxfoundation.org \
    --cc=jlovato@linuxfoundation.org \
    --cc=keith.wiles@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=spychat@gmail.com \
    --cc=web@dpdk.org \
    --cc=yasufum.o@gmail.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 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).