From: Salah Triki <salah.triki@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
Luis de Bethencourt <luisbg@osg.samsung.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Salah Triki <salah.triki@acm.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Richard Weinberger <richard@nod.at>,
linux-fsdevel@vger.kernel.org
Subject: Re: Volunteering for BeFS maintainership
Date: Wed, 27 Jul 2016 03:01:06 +0100 [thread overview]
Message-ID: <20160727020106.GA5459@pc> (raw)
In-Reply-To: <20160726175656.GC9284@thunk.org>
On Tue, Jul 26, 2016 at 01:56:56PM -0400, Theodore Ts'o wrote:
> On Tue, Jul 26, 2016 at 12:16:24AM +0100, Luis de Bethencourt wrote:
> >
> > I will wait a few days in case other people want to comment before.
> >
>
> Sounds great! Do you have a git tree set up for your befs development?
>
> And if you haven't made plans to use xfstests, I would certainly
> commend that for your consideration. Don't forget to subscribe to
> fstests@vger.kernel.org to get xfstests announcements. Also, if
> you're interested in a framework to easily run xfstests in a GCE
> (Google Compute Engine) VM, feel free to contact me.
>
> Cheers,
>
> - Ted
Thanx :)
I'm also interested in the GCE VM.
best regards,
salah
next prev parent reply other threads:[~2016-07-27 2:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:21 Volunteering for BeFS maintainership Luis de Bethencourt
2016-07-25 21:23 ` Greg KH
2016-07-25 23:16 ` Luis de Bethencourt
2016-07-26 17:56 ` Theodore Ts'o
2016-07-26 20:30 ` Luis de Bethencourt
2016-07-27 3:05 ` Theodore Ts'o
2016-07-27 11:45 ` Luis de Bethencourt
2016-07-27 13:23 ` Theodore Ts'o
2016-07-27 14:39 ` Luis de Bethencourt
2016-07-27 2:01 ` Salah Triki [this message]
2016-07-26 23:54 ` Salah Triki
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=20160727020106.GA5459@pc \
--to=salah.triki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=richard@nod.at \
--cc=salah.triki@acm.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.