From: Dave Chinner <david@fromorbit.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [LSF/MM] Ride sharing
Date: Fri, 20 Apr 2018 09:59:23 +1000 [thread overview]
Message-ID: <20180419235923.GO27893@dastard> (raw)
In-Reply-To: <20180419203432.GC14024@bombadil.infradead.org>
On Thu, Apr 19, 2018 at 01:34:32PM -0700, Matthew Wilcox wrote:
> I hate renting unnecessary cars, and the various transportation companies
> offer a better deal if multiple people book at once.
>
> I'm scheduled to arrive on Sunday at 3:18pm local time if anyone wants to
> share transport. Does anyone have a wiki we can use to coordinate this?
Arriving 4.15pm sunday, so if you want to wait around for a bit I'm
happy to share...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-04-19 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 20:34 [LSF/MM] Ride sharing Matthew Wilcox
2018-04-19 23:59 ` Dave Chinner [this message]
2018-04-20 19:19 ` Theodore Y. Ts'o
2018-04-20 16:31 ` Eric Sandeen
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=20180419235923.GO27893@dastard \
--to=david@fromorbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=willy@infradead.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).