linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [ANNOUNCE] xfstests: master branch updated to ce0aa2b
Date: Mon, 28 Apr 2014 11:00:15 +1000	[thread overview]
Message-ID: <20140428010015.GL15995@dastard> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2558 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 xfs@oss.sgi.com so they can be
picked up in the next update.

The new head of the master branch is commit:

ce0aa2b common: Use _require_xfs_io_command() instead of helpers

New Commits:

Dave Chinner (6):
      [31a50c7] generic/204: tweak reserve pool size
      [ca93123] generic: cleanup space after test in TESTDIR
      [9d7807d] xfs: remove dmapi tests from the auto group
      [03227f9] filter: xfs_repair emits new corruption messagse
      [a12a56f] shared/051: remove ACL count subtest
      [a841a6d] generic: introduce new large ACL test

Lukas Czerner (1):
      [ce0aa2b] common: Use _require_xfs_io_command() instead of helpers


Code Diffstat:

 common/attr           |  31 ++++++++++++
 common/defrag         |   2 +-
 common/rc             |  41 ---------------
 common/repair         |   3 ++
 tests/btrfs/026       |   2 +-
 tests/btrfs/027       |   2 +-
 tests/btrfs/028       |   2 +-
 tests/btrfs/047       |   2 +-
 tests/ext4/001        |   2 +-
 tests/ext4/002        |   2 +-
 tests/generic/009     |   2 +-
 tests/generic/012     |   8 +--
 tests/generic/016     |   8 +--
 tests/generic/017     |   4 +-
 tests/generic/021     |   8 +--
 tests/generic/022     |   8 +--
 tests/generic/026     | 132 ++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/026.out |   9 ++++
 tests/generic/070     |   1 +
 tests/generic/204     |   2 -
 tests/generic/213     |   2 +-
 tests/generic/214     |   2 +-
 tests/generic/223     |   2 +-
 tests/generic/228     |   2 +-
 tests/generic/255     |   6 +--
 tests/generic/256     |   2 +-
 tests/generic/274     |   2 +-
 tests/generic/300     |   4 +-
 tests/generic/311     |   2 +-
 tests/generic/312     |   2 +-
 tests/generic/316     |   4 +-
 tests/generic/group   |   1 +
 tests/shared/051      |  45 -----------------
 tests/shared/051.out  | 135 --------------------------------------------------
 tests/shared/298      |   2 +-
 tests/xfs/252         |   4 +-
 tests/xfs/290         |   2 +-
 tests/xfs/292         |   2 +
 tests/xfs/group       |  50 +++++++++----------
 39 files changed, 249 insertions(+), 293 deletions(-)
 create mode 100644 tests/generic/026
 create mode 100644 tests/generic/026.out
-- 
Dave Chinner
david@fromorbit.com

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2014-04-28  1:00 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=20140428010015.GL15995@dastard \
    --to=david@fromorbit.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@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).