From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: Slack details
Date: Mon, 07 Oct 2019 17:48:20 +0000 [thread overview]
Message-ID: <b17e36e34e65ad5261910ea306232f86e62b584b.camel@intel.com> (raw)
In-Reply-To: EA913ED399BBA34AA4EAC2EDC24CDD00C6D2A56F@FMSMSX105.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
The invite link on https://spdk.io/community is now fixed. The link was
previously set to never expire, but somehow Slack decided it had expired anyway.
On Mon, 2019-10-07 at 16:07 +0000, Howell, Seth wrote:
> Hi Geoffrey,
>
> Thanks for the heads up about the slack link. We'll get that fixed to be
> persistent. In the meantime, I have sent you an invite directly.
>
> Thanks,
>
> Seth
>
> -----Original Message-----
> From: geoff(a)hostfission.com [mailto:geoff(a)hostfission.com]
> Sent: Saturday, October 5, 2019 7:29 PM
> To: spdk(a)lists.01.org
> Subject: [SPDK] Slack details
>
> Hi Everyone,
>
> It seems the slack details listed on the website are out of date, I would like
> to join in as I have been working to debug and fix an issue with the RAID
> BDEV.
>
> Kind Regards,
> Geoffrey McRae
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
next reply other threads:[~2019-10-07 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 17:48 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-07 16:07 [SPDK] Re: Slack details Howell, Seth
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=b17e36e34e65ad5261910ea306232f86e62b584b.camel@intel.com \
--to=spdk@lists.01.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