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 610e44c
Date: Wed, 9 Apr 2014 10:12:10 +1000 [thread overview]
Message-ID: <20140409001210.GO27017@dastard> (raw)
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.
This update fixes the SCRATCH_DEV_POOL config file regression.
The new head of the master branch is commit:
610e44c check: fix wallclock wrapping problem
New Commits:
Lukas Czerner (3):
[f00a444] config: Fix SCRATCH_DEV_POOL handling
[7407717] config: Unset SCRATCH_DEV when deduced from SCRATCH_DEV_POOL
[e0f5daf] config: Fix setting FSTYP automatically
Wanlong Gao (1):
[610e44c] check: fix wallclock wrapping problem
Code Diffstat:
check | 10 +---------
common/config | 33 ++++++++++++++++++++++++++-------
2 files changed, 27 insertions(+), 16 deletions(-)
--
Dave Chinner
david@fromorbit.com
reply other threads:[~2014-04-09 0:13 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=20140409001210.GO27017@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).