From: Rich Johnston <rjohnston@sgi.com> To: Eric Sandeen <sandeen@sandeen.net> Cc: Eric Sandeen <esandeen@redhat.com>, Dave Chinner <david@fromorbit.com>, Eric Sandeen <sandeen@redhat.com>, "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>, "xfs@oss.sgi.com" <xfs@oss.sgi.com> Subject: Re: [PATCH 3/3 V4] xfstests: btrfs tests for basic informational commands Date: Tue, 19 Mar 2013 09:15:39 -0500 [thread overview] Message-ID: <5148730B.6020402@sgi.com> (raw) In-Reply-To: <5F46F0D0-1C1D-4F53-A2DE-9D39A85D078F@sandeen.net> This has been reverted and recommitted as test 307. Thanks --Rich commit 4f092a2e681c57394a0055a0735b8208bf83ec5f Author: Eric Sandeen <sandeen@sandeen.net> Date: Wed Mar 13 19:01:58 2013 +0000 xfstests: btrfs tests for basic informational commands Run basic btrfs information commands in various ways, performing sanity tests of: filesystem show, label, sync, and device stats (sync is included just because it's simple). These are mostly just smoke tests, although for example show by label & UUID should verify that the correct fs was shown. This also adds quite a few new filters to accommodate the output of the new commands. Cc: linux-btrfs@vger.kernel.org Signed-off-by: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Stefan Behrens <sbehrens@giantdisaster.de> Signed-off-by: Rich Johnston <rjohnston@sgi.com> commit 609b6f18b87bc19c5251c45342e0678cfbf0618c Author: Rich Johnston <rjohnston@sgi.com> Date: Tue Mar 19 08:13:12 2013 -0500 Revert "xfstests: btrfs tests for basic informational commands" This reverts commit 2730c49a3e80426167e6f9984b070883dc51d4b6. Test number was not sequential. Conflicts: group
WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com> To: Eric Sandeen <sandeen@sandeen.net> Cc: Eric Sandeen <sandeen@redhat.com>, Eric Sandeen <esandeen@redhat.com>, "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>, "xfs@oss.sgi.com" <xfs@oss.sgi.com> Subject: Re: [PATCH 3/3 V4] xfstests: btrfs tests for basic informational commands Date: Tue, 19 Mar 2013 09:15:39 -0500 [thread overview] Message-ID: <5148730B.6020402@sgi.com> (raw) In-Reply-To: <5F46F0D0-1C1D-4F53-A2DE-9D39A85D078F@sandeen.net> This has been reverted and recommitted as test 307. Thanks --Rich commit 4f092a2e681c57394a0055a0735b8208bf83ec5f Author: Eric Sandeen <sandeen@sandeen.net> Date: Wed Mar 13 19:01:58 2013 +0000 xfstests: btrfs tests for basic informational commands Run basic btrfs information commands in various ways, performing sanity tests of: filesystem show, label, sync, and device stats (sync is included just because it's simple). These are mostly just smoke tests, although for example show by label & UUID should verify that the correct fs was shown. This also adds quite a few new filters to accommodate the output of the new commands. Cc: linux-btrfs@vger.kernel.org Signed-off-by: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Stefan Behrens <sbehrens@giantdisaster.de> Signed-off-by: Rich Johnston <rjohnston@sgi.com> commit 609b6f18b87bc19c5251c45342e0678cfbf0618c Author: Rich Johnston <rjohnston@sgi.com> Date: Tue Mar 19 08:13:12 2013 -0500 Revert "xfstests: btrfs tests for basic informational commands" This reverts commit 2730c49a3e80426167e6f9984b070883dc51d4b6. Test number was not sequential. Conflicts: group _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-19 14:15 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-13 14:57 [PATCH 0/3] xfstests patches Eric Sandeen 2013-03-13 14:57 ` [PATCH 1/3] xfstests: add 274 to the prealloc group Eric Sandeen 2013-03-13 17:36 ` Rich Johnston 2013-03-13 14:57 ` [PATCH 2/3] xfstests: keep newlines out of SCRATCH_DEV_POOL Eric Sandeen 2013-03-13 14:57 ` Eric Sandeen 2013-03-13 17:43 ` Rich Johnston 2013-03-13 17:43 ` Rich Johnston 2013-03-13 17:45 ` Eric Sandeen 2013-03-13 17:45 ` Eric Sandeen 2013-03-13 14:57 ` [PATCH 3/3] xfstests: btrfs tests for basic informational commands Eric Sandeen 2013-03-13 14:57 ` Eric Sandeen 2013-03-13 15:32 ` Stefan Behrens 2013-03-13 15:32 ` Stefan Behrens 2013-03-13 16:17 ` Eric Sandeen 2013-03-13 16:17 ` Eric Sandeen 2013-03-13 17:47 ` Rich Johnston 2013-03-13 17:47 ` Rich Johnston 2013-03-13 16:38 ` [PATCH 3/3 V2] " Eric Sandeen 2013-03-13 16:38 ` Eric Sandeen 2013-03-13 18:53 ` [PATCH 3/3 V3] " Eric Sandeen 2013-03-13 18:53 ` Eric Sandeen 2013-03-13 19:00 ` Stefan Behrens 2013-03-13 19:00 ` Stefan Behrens 2013-03-13 19:01 ` [PATCH 3/3 V4] " Eric Sandeen 2013-03-13 19:01 ` Eric Sandeen 2013-03-14 13:01 ` Rich Johnston 2013-03-14 13:01 ` Rich Johnston 2013-03-14 13:35 ` Stefan Behrens 2013-03-14 13:35 ` Stefan Behrens 2013-03-15 10:16 ` Dave Chinner 2013-03-15 10:16 ` Dave Chinner 2013-03-15 13:46 ` Eric Sandeen 2013-03-15 13:46 ` Eric Sandeen 2013-03-15 14:23 ` Rich Johnston 2013-03-15 14:23 ` Rich Johnston 2013-03-15 14:36 ` Eric Sandeen 2013-03-15 14:36 ` Eric Sandeen 2013-03-18 13:30 ` Rich Johnston 2013-03-18 13:30 ` Rich Johnston 2013-03-19 14:15 ` Rich Johnston [this message] 2013-03-19 14:15 ` Rich Johnston 2013-03-14 17:16 ` [PATCH 0/3] xfstests patches Rich Johnston 2013-03-15 5:43 ` Dave Chinner 2013-03-15 13:38 ` Rich Johnston
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=5148730B.6020402@sgi.com \ --to=rjohnston@sgi.com \ --cc=david@fromorbit.com \ --cc=esandeen@redhat.com \ --cc=linux-btrfs@vger.kernel.org \ --cc=sandeen@redhat.com \ --cc=sandeen@sandeen.net \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.