public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 0fd43f3f4bd7
Date: Sun, 22 Sep 2019 23:24:51 +0800	[thread overview]
Message-ID: <5d87924a.1c69fb81.11deb.056a@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

Hi all,

The master branch of the xfstests repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git

have just been updated. Instead of adding new tests, two xfs tests have been
removed. And _require_renameat2 gains ability to check for specific rename
flag. 

Thanks,
Eryu

The new head of the master branch is commit:

0fd43f3f4bd7 xfs/14[89]: Remove xfs_prepair64 and xfs_prepair tests

New commits:

Qu Wenruo (1):
      [8e5bf2d06fdc] btrfs/028: Don't pollute golden output for killing already finished process

Yang Xu (1):
      [0fd43f3f4bd7] xfs/14[89]: Remove xfs_prepair64 and xfs_prepair tests

kaixuxia (1):
      [4908565469c5] common: check if a given rename flag is supported in _require_renameat2


Code Diffstat:

 common/renameat2  |  33 +++++-
 tests/btrfs/028   |   2 +-
 tests/generic/023 |   2 +-
 tests/generic/024 |  13 +--
 tests/generic/025 |  13 +--
 tests/generic/078 |  13 +--
 tests/generic/398 |   2 +-
 tests/generic/419 |   2 +-
 tests/xfs/148     |  93 -----------------
 tests/xfs/148.out | 299 ------------------------------------------------------
 tests/xfs/149     | 112 --------------------
 tests/xfs/149.out | 123 ----------------------
 tests/xfs/group   |   2 -
 13 files changed, 44 insertions(+), 665 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2019-09-22 15:25 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=5d87924a.1c69fb81.11deb.056a@mx.google.com \
    --to=guaneryu@gmail.com \
    --cc=fstests@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