From: Jan Schmidt <list.xfs@jan-o-sch.net>
To: xfs@oss.sgi.com
Cc: linux-btrfs@vger.kernel.org, sbehrens@giantdisaster.de
Subject: [PATCH v2 0/2] xfstest btrfs/316: test send / receive (was: btrfs/314)
Date: Wed, 24 Jul 2013 17:07:27 +0200 [thread overview]
Message-ID: <1374678449-21780-1-git-send-email-list.xfs@jan-o-sch.net> (raw)
From: root <root@zarzz.(none)>
These two patches add the announced tests for btrfs send / receive. As
requested, the fssum tool is now included.
One drawback is that I'm unable to edit configure.ac or whatever needs
to be modified in an autotools preferred way. Any hints appreciated,
preferrably hints containing all the modifications required to introduce
something like HAVE_SEEK_HOLE.
I do not want to make modifications to fssum.c here, if that's
absolutely required (because one /could/ get along using linux/fs.h,
which is not the way I would like to go), I'd like to have that changed
in the far-progs repository where fssum.c comes from as well.
Jan Schmidt (2):
xfstests: add fssum tool
xfstests btrfs/316: test send / receive
.gitignore | 1 +
README | 3 +
common/config | 2 +
src/Makefile | 11 +-
src/fssum.c | 819 +++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/316 | 113 +++++++
tests/btrfs/316.out | 4 +
tests/btrfs/group | 1 +
8 files changed, 953 insertions(+), 1 deletions(-)
create mode 100644 src/fssum.c
create mode 100755 tests/btrfs/316
create mode 100644 tests/btrfs/316.out
--
1.7.2.5
next reply other threads:[~2013-07-24 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 15:07 Jan Schmidt [this message]
2013-07-24 15:07 ` [PATCH v2 1/2] xfstests: add fssum tool Jan Schmidt
2013-08-06 20:42 ` Josef Bacik
2013-07-24 15:07 ` [PATCH v2 2/2] xfstests btrfs/316: test send / receive Jan Schmidt
2013-08-06 20:43 ` Josef Bacik
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=1374678449-21780-1-git-send-email-list.xfs@jan-o-sch.net \
--to=list.xfs@jan-o-sch.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--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).