From: "Ahmed Kamal" <email.ahmedkamal@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: QA suite plans
Date: Wed, 16 Jul 2008 12:06:00 +0300 [thread overview]
Message-ID: <3da3b5b40807160206h1e07033fu3fba59fd5edd7aa1@mail.gmail.com> (raw)
In-Reply-To: <3da3b5b40807160139w4b8e3474te113980d0086ba9c@mail.gmail.com>
Hi Team,
I have been following the btrfs project since Chris announced it last
year. I am happy to see v1.0 is planned in Q4. This is awesome, we can
finally get something like ZFS on Linux. The project pace is nothing
short of amazing. Thank you :)
I notice the plans contain "QA suite".
I would like to ask if there are any written plans for this QA suite yet ?
Is the suite going to be kernel code, or is it basically going to be a
set of scripts using btrfs userspace commands for regression testing ?
Thank you
next parent reply other threads:[~2008-07-16 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3da3b5b40807160139w4b8e3474te113980d0086ba9c@mail.gmail.com>
2008-07-16 9:06 ` Ahmed Kamal [this message]
2008-07-16 12:05 ` QA suite plans Josef Bacik
2008-07-16 13:22 ` Ahmed Kamal
2008-07-17 14:25 ` Miguel Sousa Filipe
2008-07-18 16:30 ` Ahmed Kamal
2008-07-18 16:36 ` Tim Gelter
2008-07-18 18:20 ` Problems building btrfs Chris Mason
2008-07-18 18:51 ` tgelter
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=3da3b5b40807160206h1e07033fu3fba59fd5edd7aa1@mail.gmail.com \
--to=email.ahmedkamal@googlemail.com \
--cc=linux-btrfs@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