CEPH filesystem development
 help / color / mirror / Atom feed
From: "Piotr Dałek" <branch@predictor.org.pl>
To: Mark Nelson <mnelson@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: 11/23/2016 Weekly Ceph Performance Meeting IS ON!
Date: Wed, 23 Nov 2016 21:31:47 +0100	[thread overview]
Message-ID: <20161123203147.GF26997@predictor> (raw)
In-Reply-To: <cb6d61ef-c2c0-3499-7580-a1b8df0a94f6@redhat.com>

On Wed, Nov 23, 2016 at 09:51:30AM -0600, Mark Nelson wrote:
> 8AM PST as usual!  Ben Niven-Jenkins from Nokia will be stopping by
> to give a presentation on bluestore testing they've been doing at
> Nokia. Why work on the day before Thanksgiving when you can listen
> to an interesting presentation! :D  See you there!

Any chance to have today's recording posted somewhere?

-- 
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl

      reply	other threads:[~2016-11-23 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 15:51 11/23/2016 Weekly Ceph Performance Meeting IS ON! Mark Nelson
2016-11-23 20:31 ` Piotr Dałek [this message]

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=20161123203147.GF26997@predictor \
    --to=branch@predictor.org.pl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mnelson@redhat.com \
    /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