From: "Jörn Engel" <joern@logfs.org>
To: amagai@osrg.net
Cc: andi@firstfloor.org, linux-fsdevel@vger.kernel.org
Subject: Re: NILFS version 2 now available
Date: Mon, 18 Jun 2007 13:29:04 +0200 [thread overview]
Message-ID: <20070618112904.GC21275@lazybastard.org> (raw)
In-Reply-To: <20070618045000.0C0123E0694@fs.osrg.net>
On Mon, 18 June 2007 13:50:00 +0900, amagai@osrg.net wrote:
>
> We will hold a BOF session in Linux Symposium Ottawa June, 2007,
> titled "Filesystem support for continuous snapshotting". Please join
> to discuss you're interested in snapshotting.
I'd like to join, however I won't be in Ottawa. Any chance you'd make
it to linuxconf.eu?
Jörn
--
When in doubt, use brute force.
-- Ken Thompson
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-06-18 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 2:42 NILFS version 2 now available amagai
2007-06-17 18:35 ` Andi Kleen
2007-06-17 21:42 ` Jörn Engel
2007-06-18 4:50 ` amagai
2007-06-18 11:29 ` Jörn Engel [this message]
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=20070618112904.GC21275@lazybastard.org \
--to=joern@logfs.org \
--cc=amagai@osrg.net \
--cc=andi@firstfloor.org \
--cc=linux-fsdevel@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).