From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
Patrick MacArthur <pmacarth@iol.unh.edu>,
"alialnu@mellanox.com" <alialnu@mellanox.com>
Subject: Re: [dpdk-dev] [dpdk-ci] maintenance on DPDK patchwork today
Date: Wed, 6 Jun 2018 15:22:29 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F3626C4@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <8307392.n27avdQmPa@xps>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, June 6, 2018 3:03 PM
> To: dev@dpdk.org
> Cc: ci@dpdk.org; dpdklab@iol.unh.edu; Patrick MacArthur
> <pmacarth@iol.unh.edu>; alialnu@mellanox.com
> Subject: Re: [dpdk-dev] [dpdk-ci] maintenance on DPDK patchwork today
>
> 06/06/2018 08:56, Thomas Monjalon:
> > Patchwork will stop working during approximately one hour or hopefully
> > less, today June 6th.
> > It will be upgraded to patchwork 2.
> >
> > Sorry for the inconvenience.
>
> The upgrade to patchwork 2.0.2 is now done:
\o/ Well done.
John
next prev parent reply other threads:[~2018-06-06 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 6:56 [dpdk-dev] " Thomas Monjalon
2018-06-06 14:03 ` [dpdk-dev] [dpdk-ci] " Thomas Monjalon
2018-06-06 15:22 ` Mcnamara, John [this message]
2018-06-06 16:23 ` Mcnamara, John
2018-06-18 23:08 ` [dpdk-dev] " Dan Gora
2018-06-18 23:21 ` Thomas Monjalon
2018-06-18 23:26 ` Dan Gora
2018-06-18 23:47 ` Dan Gora
2018-06-19 8:58 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE23F3626C4@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=alialnu@mellanox.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=pmacarth@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).