linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kiran Patil <kirantpatil@gmail.com>
To: Eric Sandeen <sandeen@redhat.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, 7 Jan 2013 22:39:20 +0530	[thread overview]
Message-ID: <CANT588tRL+DoFvyfkaFHsEFPke-C9-mn-0nyooWY04gOYfErtA@mail.gmail.com> (raw)
In-Reply-To: <CANT588t+jcOZNv4w1azXkuywEbSh_+F_AtrUo=3=1P4j+Aesjw@mail.gmail.com>

On Mon, Jan 7, 2013 at 10:31 PM, Kiran Patil <kirantpatil@gmail.com> wrote:
> On Mon, Jan 7, 2013 at 9:28 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>> 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
>>
> Dear Eric and David,
>
> Thanks a lot for your inputs.
>
> We will work on them and soon we will start our work.
>
> Thank you,
>
> -Kiran

Sorry, I forgot to say thanks to Liu and Arne.

Thank you Liu and Arne for your suggestions.

-Kiran

      reply	other threads:[~2013-01-07 17:09 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
2013-01-07 17:01     ` Kiran Patil
2013-01-07 17:09       ` Kiran Patil [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=CANT588tRL+DoFvyfkaFHsEFPke-C9-mn-0nyooWY04gOYfErtA@mail.gmail.com \
    --to=kirantpatil@gmail.com \
    --cc=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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).