lustre-devel-lustre.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] New slack chat room for linux client work
Date: Sat, 7 Jul 2018 00:18:26 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1807070013470.6125@casper.infradead.org> (raw)
In-Reply-To: <88A13941-47CB-4D08-8CA8-4FD041487322@cray.com>


> James, Slack tells me:
> "Don't have an @whamcloud.com email address? 
> Contact your Workspace Administrator for an invitation."

Yeah slack doesn't seem to be a open to anyone platform. You have to ask
the admin (me in this case) if you can join. I can let people in the same
domain like whamcloud.com or cray.com to join.

> 
> -Cory
> 
> -- 
> 
> ?On 7/6/18, 9:34 AM, "lustre-devel on behalf of James Simmons" <lustre-devel-bounces at lists.lustre.org on behalf of jsimmons@infradead.org> wrote:
> 
>     
>     Some people have asked for a chat room since it can be difficult
>     to filter between the mixture of patches and technical discusssions
>     going on here. If people are interested to join the site is below
>     
>     https://lustreupstreamclient.slack.com/messages/CAV4QF0ER/
>     _______________________________________________
>     lustre-devel mailing list
>     lustre-devel at lists.lustre.org
>     http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>     
> 
> 

  reply	other threads:[~2018-07-06 23:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 14:33 [lustre-devel] New slack chat room for linux client work James Simmons
2018-07-06 16:26 ` Cory Spitz
2018-07-06 23:18   ` James Simmons [this message]
2020-01-28 18:23     ` Nikitas Angelinas
2020-01-29  0:49       ` James Simmons
2020-01-30 23:04         ` Spitz, Cory James

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=alpine.LFD.2.21.1807070013470.6125@casper.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=lustre-devel@lists.lustre.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;
as well as URLs for NNTP newsgroup(s).