From: Jia He <hejianet@gmail.com>
To: fstests@vger.kernel.org
Cc: Jia He <hejianet@gmail.com>
Subject: [PATCH 1/2] fstests: comments to prevent from adding "/" to the end of 2 environment variables
Date: Thu, 7 Jan 2016 14:37:28 +0800 [thread overview]
Message-ID: <1452148649-22451-2-git-send-email-hejianet@gmail.com> (raw)
In-Reply-To: <1452148649-22451-1-git-send-email-hejianet@gmail.com>
This adds comments to prevent user from adding "/" to the end of TEST_DIR and
SCRATCH_MNT
Signed-off-by: Jia He <hejianet@gmail.com>
---
configs/example.config | 1 +
configs/localhost.config | 1 +
2 files changed, 2 insertions(+)
diff --git a/configs/example.config b/configs/example.config
index 7b6e142..cf8f08e 100644
--- a/configs/example.config
+++ b/configs/example.config
@@ -1,5 +1,6 @@
# Example config file with all typical device options set for full
# XFS kernel, progs and dump testing.
+# please do NOT add "/" to end of TEST_DIR and SCRATCH_MNT
MODULAR=0
SCRATCH_MNT=/mnt/scratch
SCRATCH_DEV=/dev/sdb5
diff --git a/configs/localhost.config b/configs/localhost.config
index f47e694..a7b9fe3 100644
--- a/configs/localhost.config
+++ b/configs/localhost.config
@@ -1,5 +1,6 @@
# default localhost file, set up for virtual machines using KVM and
# virtio for it's block devices
+# Please do NOT add "/" to the end of TEST_DIR and SCRATCH_MNT
#
MODULAR=0
TEST_DIR=/mnt/test
--
2.1.4
next prev parent reply other threads:[~2016-01-07 6:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 6:37 [PATCH 0/2] fstests: help user to troubleshoot the re-mount issue quickly Jia He
2016-01-07 6:37 ` Jia He [this message]
2016-01-07 10:27 ` [PATCH 1/2] fstests: comments to prevent from adding "/" to the end of 2 environment variables Eryu Guan
2016-01-07 14:03 ` hejianet
2016-01-08 9:39 ` Eryu Guan
2016-01-08 13:28 ` hejianet
2016-01-07 6:37 ` [PATCH 2/2] fstests: give user friendly prompts for already mounted dir Jia He
2016-01-10 23:29 ` Dave Chinner
2016-01-11 5:20 ` hejianet
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=1452148649-22451-2-git-send-email-hejianet@gmail.com \
--to=hejianet@gmail.com \
--cc=fstests@vger.kernel.org \
/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