From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: dpdk-web <web@dpdk.org>
Subject: [dpdk-web] Fwd: code.dpdk.org down
Date: Sat, 31 Oct 2020 12:50:26 -0400 [thread overview]
Message-ID: <CAFXL6f_3iiBx1WxjFh2vAO7yprmiXvivFKPmhwX7WdDXvMKD4g@mail.gmail.com> (raw)
In-Reply-To: <2BD8BF03-F789-44FA-A2FD-26ED95BAE966@intel.com>
FYI: Can someone assist with this?
Thanks.
Trishan
---------- Forwarded message ---------
From: St Leger, Jim <jim.st.leger@intel.com>
Date: Sat, Oct 31, 2020 at 11:40 AM
Subject: Re: code.dpdk.org down
To: Morten Brørup <mb@smartsharesystems.com>, Thomas Monjalon <
thomas@monjalon.net>, Trishan de Lanerolle <tdelanerolle@linuxfoundation.org
>
Hopefully Thomas and/or Trishan have some ideas.
Jim
On Oct 31, 2020, at 01:09, Morten Brørup <mb@smartsharesystems.com> wrote:
Jim,
It's not clear to me how to report this infrastructure problem, so I hope
you can pass it on to the right person:
Accessing code.dpdk.org yields a 502 Bad Gateway response.
E.g.:
http://code.dpdk.org/dpdk/latest/source/lib
Med venlig hilsen / kind regards
*Morten Brørup*
CTO
*SmartShare Systems A/S*
Tonsbakken 16-18
DK-2740 Skovlunde
Denmark
Office +45 70 20 00 93
Direct +45 89 93 50 22
Mobile +45 25 40 82 12
mb@smartsharesystems.com
www.smartsharesystems.com
--
Trishan R. de Lanerolle
Technical Program Manager & Community Architect
Networking, Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle
email: tdelanerolle@linuxfoundation.org
next parent reply other threads:[~2020-10-31 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98CBD80474FA8B44BF855DF32C47DC35C613C9@smartserver.smartshare.dk>
[not found] ` <2BD8BF03-F789-44FA-A2FD-26ED95BAE966@intel.com>
2020-10-31 16:50 ` Trishan de Lanerolle [this message]
2020-10-31 17:21 ` Ali Alnubani
2020-10-31 21:47 ` Trishan de Lanerolle
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=CAFXL6f_3iiBx1WxjFh2vAO7yprmiXvivFKPmhwX7WdDXvMKD4g@mail.gmail.com \
--to=tdelanerolle@linuxfoundation.org \
--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).