From: Erwan Velu <evelu@redhat.com>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: BlueStore deep-dive over bluejeans
Date: Thu, 25 Feb 2016 08:59:20 -0500 (EST) [thread overview]
Message-ID: <1897606090.36976108.1456408760977.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1602241447430.7555@cpach.fuggernut.com>
I cannot attend but will watch the recording.
If you can paste it on this thread, would be nice.
Thx,
----- Original Message -----
From: "Sage Weil" <sweil@redhat.com>
To: ceph-devel@vger.kernel.org
Sent: Wednesday, February 24, 2016 8:51:39 PM
Subject: BlueStore deep-dive over bluejeans
Hey all,
I'm planning on doing an hour-ish deep-dive into the inner workings of
BlueStore next Monday, 2/29, 5pm-6pm ET / 2pm-3pm PT. It'll be a
mostly-informal brain dump and walk-through of the code over bluejeans,
and we'll record it. Anyone who is or is planning to be involved in
bluestore development, please join and ask questions etc! I'll send out
the bluejeans link shortly before we start.
sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-25 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 19:51 BlueStore deep-dive over bluejeans Sage Weil
2016-02-25 13:59 ` Erwan Velu [this message]
2016-02-29 21:01 ` Sage Weil
2016-03-01 15:19 ` Sage Weil
2016-03-02 13:36 ` Sage Weil
2016-03-02 13:55 ` Sage Weil
2016-03-03 4:08 ` Dan Mick
2016-03-03 4:14 ` Haomai Wang
2016-03-03 13:19 ` Sage Weil
2016-03-05 10:41 ` huang jun
2016-03-05 18:54 ` Sage Weil
[not found] ` <20160306184642014525100@chinanetcenter.com>
2016-03-06 16:34 ` Sage Weil
2016-04-12 8:33 ` chen kael
2016-04-12 17:43 ` Sage Weil
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=1897606090.36976108.1456408760977.JavaMail.zimbra@redhat.com \
--to=evelu@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@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