From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: actually hook up 198, make it generic
Date: Thu, 30 Jul 2009 11:15:49 -0500 [thread overview]
Message-ID: <4A71C735.1080004@sandeen.net> (raw)
In-Reply-To: <4A71BE6F.4030609@sandeen.net>
Eric Sandeen wrote:
> Christoph Hellwig wrote:
...
>> Did we manage to get a proper copyright / license statement for this
>> one.
>
> hadn't looked into it; I'll ping Daniel McNeil who seems to be the
> original author ...?
>
> But I'll fix it and worry about the copyright later, since it's already
> in ...
>
> -Eric
>
Actually there's a whole whack of nice tests at
http://devresources.linux-foundation.org/daniel/AIO/TESTS/
But I'm having trouble finding Daniel ...
Seems like they'd all be good to pull in; one test per test, I guess.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-30 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 18:07 [PATCH] xfstests: actually hook up 198, make it generic Eric Sandeen
2009-07-30 15:27 ` Christoph Hellwig
2009-07-30 15:38 ` Eric Sandeen
2009-07-30 16:15 ` Eric Sandeen [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=4A71C735.1080004@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.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