linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Kiran Patil <kirantpatil@gmail.com>
Cc: linux-btrfs@vger.kernel.org, bo.li.liu@oracle.com,
	xfs-oss <xfs@oss.sgi.com>
Subject: Re: Open for contribution towards xfstests for btrfs
Date: Mon, 07 Jan 2013 09:58:10 -0600	[thread overview]
Message-ID: <50EAF092.20907@redhat.com> (raw)
In-Reply-To: <CANT588tZd8y3G0jZD3Ti-nHexk1jwmD-fJP1f1bttFP8kyEgqg@mail.gmail.com>

On 1/7/13 4:18 AM, Kiran Patil wrote:
> Hello,
> 
> We have a team of 5 students who would like to contribute to btrfs
> filesystem testing using xfstests.
> 
> Is there space for them to contribute?
> 
> If yes, to whom do they need to keep in touch for guidance.

(cc: xfs list)

Are you thinking of writing new tests, or doing more formal testing
with the existing testsuite?  Both would be useful.

In particular, any time there's a bugfix, a regression test is helpful.
Generic new tests of btrfs functionality would be good, too.

I would suggest starting with a couple new tests, and cc: the xfs list
for review.  In the course of the review you'll get a sense of the various
conventions used in xfstests, etc.

Simply running xfstests over various btrfs configurations would also
be useful, to be sure any regressions caught by existing tests don't go
unnoticed.

thanks,
-Eric

> Thank you,
> Kiran Patil (Director)
> Green Turtles Technologies, INDIA.



  parent reply	other threads:[~2013-01-07 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANT588vv8xYNWGBSZUDu0vui2ZH4QqL7tvQX8zOGof7nucC6_Q@mail.gmail.com>
2013-01-07 10:18 ` Open for contribution towards xfstests for btrfs Kiran Patil
2013-01-07 13:01   ` Liu Bo
2013-01-07 14:36     ` Arne Jansen
2013-01-07 15:31   ` David Sterba
2013-01-07 18:03     ` Eric Sandeen
2013-01-08  2:03       ` Kiran Patil
2013-01-07 15:58   ` Eric Sandeen [this message]
2013-01-07 17:01     ` Kiran Patil
2013-01-07 17:09       ` Kiran Patil

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=50EAF092.20907@redhat.com \
    --to=sandeen@redhat.com \
    --cc=bo.li.liu@oracle.com \
    --cc=kirantpatil@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /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).