From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [ANNOUNCE] xfstests: master branch updated to 45d1fac
Date: Tue, 27 May 2014 12:44:37 +1000 [thread overview]
Message-ID: <20140527024437.GC8554@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]
Hi folks,
The xfstests repository at git://oss.sgi.com/xfs/cmds/xfstests has
just been updated. Patches often get missed, so please check if your
outstanding patches were in this update. If they have not been in
this update, please resubmit them to fstests@vger.kernel.org so they
can be picked up in the next update.
I've sent this announcement to fstests, linux-fsdevel and the XFS,
ext4 and btrfs lists. Future fstests announcements will only be
directed to the fstests and linux-fsdevel lists.
The new head of the master branch is commit:
45d1fac btrfs: test for btrfs send when nested subvols/snapshots exist
New Commits:
Eryu Guan (2):
[82afae2] generic: new ENOSPC regression test
[caca581] xfs/005: filter _scratch_mount output to match golden image
Filipe David Borba Manana (5):
[e7dd9f1] btrfs: add test for btrfs send with long paths
[86da66c] common: add helper require function _require_btrfs_cloner
[d140277] btrfs: add test for clone operation
[3318629] btrfs: add test for btrfs send with large xattrs
[45d1fac] btrfs: test for btrfs send when nested subvols/snapshots exist
Code Diffstat:
common/rc | 7 +
tests/btrfs/035 | 4 +-
tests/btrfs/051 | 85 +++++++++
tests/btrfs/051.out | 1 +
tests/btrfs/052 | 171 +++++++++++++++++
tests/btrfs/052.out | 499 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/053 | 109 +++++++++++
tests/btrfs/053.out | 1 +
tests/btrfs/054 | 109 +++++++++++
tests/btrfs/054.out | 1 +
tests/btrfs/group | 4 +
tests/generic/027 | 107 +++++++++++
tests/generic/027.out | 2 +
tests/generic/group | 1 +
tests/xfs/005 | 7 +-
15 files changed, 1104 insertions(+), 4 deletions(-)
create mode 100755 tests/btrfs/051
create mode 100644 tests/btrfs/051.out
create mode 100755 tests/btrfs/052
create mode 100644 tests/btrfs/052.out
create mode 100755 tests/btrfs/053
create mode 100644 tests/btrfs/053.out
create mode 100755 tests/btrfs/054
create mode 100644 tests/btrfs/054.out
create mode 100755 tests/generic/027
create mode 100644 tests/generic/027.out
--
Dave Chinner
david@fromorbit.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2014-05-27 2:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140527024437.GC8554@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).