From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfstests: add local.config example
Date: Thu, 16 Sep 2010 13:07:47 -0500 [thread overview]
Message-ID: <4C925CF3.3060303@sandeen.net> (raw)
I think it'd be useful to have a local.config template in the
git repo, to avoid having to re-read the README each time
to remember the required environment variable names.
Thoughts? Am I just lazy? :)
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
diff --git a/local.config b/local.config.example
new file mode 100644
index 0000000..6b2e0e9
--- /dev/null
+++ b/local.config.example
@@ -0,0 +1,10 @@
+# Ideally define at least these 4 to match your environment
+# The first 2 are required.
+# See README for other variables which can be set.
+#
+# Note: SCRATCH_DEV >will< get overwritten!
+
+export TEST_DEV=/dev/sdX1
+export TEST_DIR=/mnt/test
+export SCRATCH_DEV=/dev/sdX2
+export SCRATCH_MNT=/mnt/scratch
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-09-16 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 18:07 Eric Sandeen [this message]
2010-09-16 23:31 ` [PATCH] xfstests: add local.config example Dave Chinner
2012-10-26 15:55 ` 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=4C925CF3.3060303@sandeen.net \
--to=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: 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