From: Ben Myers <bpm@sgi.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Mark Tinguely <tinguely@sgi.com>,
xfs@oss.sgi.com
Subject: Re: Anyone have test cases for SEEK_HOLE/SEEK_DATA?
Date: Tue, 18 Sep 2012 13:28:41 -0500 [thread overview]
Message-ID: <20120918182841.GA3343@sgi.com> (raw)
In-Reply-To: <20120918181556.GC28689@thunk.org>
Hey Ted,
On Tue, Sep 18, 2012 at 02:15:56PM -0400, Theodore Ts'o wrote:
> On Tue, Sep 18, 2012 at 09:43:36AM -0500, Mark Tinguely wrote:
> > xfstest 285 and 286 (I believe these tests were only in the OSS
> > version and not in the kernel.org developers version of xfstests).
>
> Could you clarify what the relationship is between the OSS xfstests
> tree and the one on kernel.org? Is the OSS tree always ahead of the
> kernel.org tree (i.e., are the commits in the OSS tree a superset of
> the ones in the kernel.org tree)?
The trees on kernel.org are being retired. I'm not sure what Christoph is
going to do with the kernel.org repos, but expect new changes to go directly
into the xfstests repo on oss.sgi.com.
> I had been under the impression that commits flowed from the
> kernel.org tree to the OSS tree, but it sounds like I was misinformed
> on that point?
Your impression is just a few days out of date. See:
http://oss.sgi.com/archives/xfs/2012-09/msg00156.html
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-18 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nsxa9wojdcd.fsf@closure.thunk.org>
2012-09-18 6:40 ` Anyone have test cases for SEEK_HOLE/SEEK_DATA? Dave Chinner
2012-09-18 14:43 ` Mark Tinguely
2012-09-18 18:15 ` Theodore Ts'o
2012-09-18 18:20 ` Eric Sandeen
2012-09-18 18:28 ` Ben Myers [this message]
2012-09-18 18:42 ` Theodore Ts'o
2012-09-18 19:03 ` Ben Myers
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=20120918182841.GA3343@sgi.com \
--to=bpm@sgi.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tinguely@sgi.com \
--cc=tytso@mit.edu \
--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