From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [PATCH] xfstests: remove recursive include in filter.btrfs
Date: Sun, 21 Apr 2013 01:27:24 -0500 [thread overview]
Message-ID: <517386CC.8010406@redhat.com> (raw)
Not sure how this happened, but filter.btrfs including
itself leads to immense sadness for any file that includes it.
(I got a segfault when I tried to run 307)
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/common/filter.btrfs b/common/filter.btrfs
index b1aa733..99d04a6 100644
--- a/common/filter.btrfs
+++ b/common/filter.btrfs
@@ -1,7 +1,5 @@
# Filters for btrfs command output
-. ./common/filter.btrfs
-
# Some, but not all, commands emit "Btrfs <version>"
_filter_btrfs_version()
{
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-04-21 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 6:27 Eric Sandeen [this message]
[not found] ` <51746D07.5090300@sandeen.net>
2013-04-21 22:51 ` [PATCH V3] xfstests: fix common filter include in filter.btrfs Eric Sandeen
2013-04-22 13:45 ` Rich Johnston
2013-04-22 14:36 ` [PATCH] xfstests: remove recursive " 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=517386CC.8010406@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@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