All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: 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: Tue, 26 Jul 2016 23:05:51 -0400	[thread overview]
Message-ID: <20160727030551.GD9284@thunk.org> (raw)
In-Reply-To: <5797C855.8090005@osg.samsung.com>

On Tue, Jul 26, 2016 at 09:30:13PM +0100, Luis de Bethencourt wrote:
> > 
> > Sounds great!  Do you have a git tree set up for your befs development?
> 
> Yes, I have the following in github (if that is OK):
> https://github.com/luisbg/linux-befs
> 
> I have two branches there based on Linus' master:
>  - befs-linus: with patches Andrew Morton has approved
>  - befs-next: with patches I've tested but that remain under review

So it sounds like you plan to send patches through Andrew's tree.
That works fine, although if you end up sending a larger number of
patches through the linux-mm tree, it might make sense for you to send
patches to Linus directly.  So if you have a chance to get a GPG key
which is signed by people in the Kernel keyring, that would be a good
preparation for that eventuality.  That will require face-to-face
verification of your identity by people who are already in the GPG web
of trust, so it's good to plan for that in advance.

> It would be amazing to have a framework to run xfstests in a GCE VM.

Please see:

       https://thunk.org/gce-xfstests

and

	https://github.com/tytso/xfstests-bld/blob/master/README.md

for more information.

I plan to do some work to make it simpler to get started using
gce-xfstests.  (Specifically, so you don't have to build the tree and
generate your own GCE image, but instead using a premade one.)

Are there userspace tools available to create and consistency check
BeFS file systems?  If so, I can try to get those included into the
test appliance image.  (Better yet, if you can arrange to have someone
create a debian package for BeFStools, that would be great.)

						- Ted

  reply	other threads:[~2016-07-27  3:06 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 [this message]
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
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=20160727030551.GD9284@thunk.org \
    --to=tytso@mit.edu \
    --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=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.