DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ali Alnubani <alialnu@mellanox.com>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] add section for mail archives
Date: Wed, 29 May 2019 16:07:08 +0100	[thread overview]
Message-ID: <c9830802-73b8-1303-a6dd-aa410ab33133@intel.com> (raw)
In-Reply-To: <20190521132708.30254-1-alialnu@mellanox.com>

On 5/21/2019 2:27 PM, Ali Alnubani wrote:
> The section advertises the new public-inbox archives>
> Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
> ---
>  content/contribute/_index.md | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/content/contribute/_index.md b/content/contribute/_index.md
> index 3f498ab..eedc2be 100644
> --- a/content/contribute/_index.md
> +++ b/content/contribute/_index.md
> @@ -158,6 +158,16 @@ anybody can notify a bug to the community, and follow the resolution.
>  A notification is sent to dev@dpdk.org for every new bug.
>  The fixes must be sent and discussed on the mailing list.
>  
> +## Mailing list archives {#archives}
> +---
> +
> +The dev archives are available via [pipermail](//mails.dpdk.org/archives/dev/),
> +or via [public-inbox](//inbox.dpdk.org/dev/).

Hi Ali,

I wasn't aware of it.
Can you please briefly explain what is the benefit of [public-inbox]? What it
enables to do for us?

Thanks,
ferruh

> +
> +The public-inbox archives can also be accessed via [nntp](nntp://inbox.dpdk.org),
> +and provide a search engine. For more info, visit the
> +[help](http://inbox.dpdk.org/dev/_/text/help/) page.
> +
>  ## Technical Board {#board}
>  ---
>  
> 


  parent reply	other threads:[~2019-05-29 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 13:27 Ali Alnubani
2019-05-23  7:25 ` Thomas Monjalon
2019-05-29 15:07 ` Ferruh Yigit [this message]
2019-05-29 15:31   ` Ferruh Yigit
2019-05-30  7:35   ` Ali Alnubani

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=c9830802-73b8-1303-a6dd-aa410ab33133@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=alialnu@mellanox.com \
    --cc=web@dpdk.org \
    /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).