DPDK website maintenance
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "web@dpdk.org" <web@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-web] [PATCH] update the code browse link to point to elixir
Date: Sun, 1 Sep 2019 11:58:42 +0000	[thread overview]
Message-ID: <AM0PR05MB4401E39A4DD4126843DD42FDD7BF0@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <c136c98b-ad93-75c2-9eca-9b7a7f6e5162@intel.com>

Hi Ferruh,

> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Tuesday, August 27, 2019 1:48 PM
> To: Ali Alnubani <alialnu@mellanox.com>; web@dpdk.org
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Subject: Re: [dpdk-web] [PATCH] update the code browse link to point to
> elixir
> 
> On 8/27/2019 10:32 AM, Ferruh Yigit wrote:
> > On 8/5/2019 2:39 PM, Ali Alnubani wrote:
> >> The DPDK source code is indexed with the Elixir Cross-Referencer, and
> >> is available at both code.dpdk.org, and lxr.dpdk.org.
> >
> > +1, thanks :)
> >
> > I will announce this in wider internal group.
> 
> I did share, and get a comment to have this link in somewhere in dpdk.org,
> what do you think?
Do you mean in www.dpdk.org? If you do, It's already in https://www.dpdk.org/contribute/.

> 
> >
> >>
> >> Suggested-by: Thomas Monjalon <thomas@monjalon.net>
> >> Signed-off-by: Ali Alnubani <alialnu@mellanox.com>

Sorry for the late response.

Regards,
Ali

  reply	other threads:[~2019-09-01 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 13:39 Ali Alnubani
2019-08-27  9:32 ` Ferruh Yigit
2019-08-27 10:47   ` Ferruh Yigit
2019-09-01 11:58     ` Ali Alnubani [this message]
2019-09-04  8:08       ` Ferruh Yigit
2019-09-04  8:17         ` Thomas Monjalon
2019-09-04  8:28           ` Ferruh Yigit
2019-09-04  8:43             ` Ferruh Yigit

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=AM0PR05MB4401E39A4DD4126843DD42FDD7BF0@AM0PR05MB4401.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    --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).