From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: techboard@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-techboard] release manager backup
Date: Thu, 29 Jun 2017 14:48:27 +0100 [thread overview]
Message-ID: <20170629134827.GA16748@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <2018976.Gf4KLAyyyC@xps>
On Thu, Jun 29, 2017 at 03:28:41PM +0200, Thomas Monjalon wrote:
> 29/06/2017 14:59, Bruce Richardson:
> > Yes, I think this is a good idea. [What with all the buses working with
> > DPDK now, I think we need a good plan in case you get hit by one. :-P ]
>
> You overestimates how strong are those buses!
>
> Are you applying for a role as risk manager? :)
:-)
next prev parent reply other threads:[~2017-06-29 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 7:29 release manager backup Thomas Monjalon
2017-06-29 12:59 ` [dpdk-techboard] " Bruce Richardson
2017-06-29 13:28 ` Thomas Monjalon
2017-06-29 13:48 ` Bruce Richardson [this message]
2017-07-03 11:01 ` Mcnamara, John
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=20170629134827.GA16748@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@dpdk.org \
--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).