linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
	xfs <linux-xfs@vger.kernel.org>,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [External] : Shameless plug for the FS Track at LPC next week!
Date: Fri, 17 Sep 2021 16:50:07 -0700	[thread overview]
Message-ID: <20210917235007.GC10224@magnolia> (raw)
In-Reply-To: <20210917221124.GS2361455@dread.disaster.area>

On Sat, Sep 18, 2021 at 08:11:24AM +1000, Dave Chinner wrote:
> On Thu, Sep 16, 2021 at 05:38:38PM +0530, Chandan Babu R wrote:
> > On 16 Sep 2021 at 07:09, Darrick J. Wong wrote:
> > > Hi folks!
> > >
> > > The Linux Plumbers conference is next week!  The filesystems mini
> > > conference is next Tuesday, 21 September, starting at 14:00 UTC:
> > >
> > 
> > <snip>
> > 
> > >
> > > To all the XFS developers: it has been a very long time since I've seen
> > > all your faces!  I would love to have a developer BOF of some kind to
> > > see you all again, and to introduce Catherine Hoang (our newest
> > > addition) to the group.
> > >
> > > If nobody else shows up to the roadmap we could do it there, but I'd
> > > like to have /some/ kind of venue for everyone who don't find the
> > > timeslots convenient (i.e. Dave and Chandan).  This doesn't have to take
> > > a long time -- even a 15 minute meet and greet to help everyone
> > > (re)associate names with faces would go a long way towards feeling
> > > normal(ish) again. ;)
> > 
> > 14:00 UTC maps to 19:30 for me. I am fine with this time slot.
> 
> It maps to 12-4am for me. Not really practical :/

FWIW I'll try to commandeer one of the LPC hack rooms late Tuesday
evening (say around 0200 UTC) if people are interested in XFS office
hours?

(They also don't need to be on LPC's BBB instance; I /can/ host largeish
meetings on Zoom courtesy of $employer...)

--D

> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

  reply	other threads:[~2021-09-17 23:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  1:39 Shameless plug for the FS Track at LPC next week! Darrick J. Wong
2021-09-16 12:08 ` [External] : " Chandan Babu R
2021-09-17 22:11   ` Dave Chinner
2021-09-17 23:50     ` Darrick J. Wong [this message]
2021-09-18 15:21       ` James Bottomley
2021-09-17  8:30 ` Jan Kara
2021-09-17  8:36   ` Jan Kara
2021-09-17  9:38     ` Jan Kara
2021-09-17 10:23       ` Amir Goldstein
2021-09-17 16:12         ` Darrick J. Wong
2021-09-17 23:15           ` Dave Chinner
2021-09-18  7:44             ` Alternative project ids and quotas semantics (Was: Shameless plug for the FS Track at LPC next week!) Amir Goldstein
2021-09-23  0:38               ` Dave Chinner

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=20210917235007.GC10224@magnolia \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.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).