From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ali Alnubani <alialnu@mellanox.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: Tue, 27 Aug 2019 11:47:31 +0100 [thread overview]
Message-ID: <c136c98b-ad93-75c2-9eca-9b7a7f6e5162@intel.com> (raw)
In-Reply-To: <8b893f98-0cb0-fc87-28e6-b69d9e199718@intel.com>
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?
>
>>
>> Suggested-by: Thomas Monjalon <thomas@monjalon.net>
>> Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
>> ---
>> content/contribute/_index.md | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/content/contribute/_index.md b/content/contribute/_index.md
>> index 5afc23c..be2bc1a 100644
>> --- a/content/contribute/_index.md
>> +++ b/content/contribute/_index.md
>> @@ -34,7 +34,7 @@ Or if git is blocked in your network:
>> git clone http://dpdk.org/git/dpdk
>> ```
>>
>> -The source code can be [browsed online](//git.dpdk.org/dpdk/tree/).
>> +The source code can be [browsed online](//code.dpdk.org/dpdk/latest/source).
>>
>> ## Contribute by sending patches {#send}
>> ---
>>
>
next prev parent reply other threads:[~2019-08-27 10:47 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 [this message]
2019-09-01 11:58 ` Ali Alnubani
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=c136c98b-ad93-75c2-9eca-9b7a7f6e5162@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alialnu@mellanox.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).