From: Gabriel Niebler <gniebler@suse.com>
To: fstests@vger.kernel.org
Cc: Gabriel Niebler <gniebler@suse.com>
Subject: [PATCH 1/4] README: Fix environment setup quick start
Date: Thu, 3 Mar 2022 14:28:01 +0100 [thread overview]
Message-ID: <20220303132804.4151-2-gniebler@suse.com> (raw)
In-Reply-To: <20220303132804.4151-1-gniebler@suse.com>
Following the old quick start information would not get a new user to run
tests with their configuration, because it was not accurate to how the check
script actually works.
By default, the script looks for *.config files in HOST_CONFIG_DIR, which
defaults to '.config' if unset. The README now reflects that.
Signed-off-by: Gabriel Niebler <gniebler@suse.com>
---
README | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/README b/README
index 9f01aa10..7e36905e 100644
--- a/README
+++ b/README
@@ -61,8 +61,10 @@ Preparing system for tests:
- setup your environment
Quick start:
- - copy local.config.example to local.config and edit as needed
- Or:
+ - set HOST_CONFIG_DIR to a path of your choice (ideally outside the git tree)
+ - copy configs/localhost.config there and edit as needed
+ - also consult local.config.example for inspiration
+ These are the most important environment variables you may want to set there:
- setenv TEST_DEV "device containing TEST PARTITION"
- setenv TEST_DIR "mount point of TEST PARTITION"
- optionally:
--
2.35.1
next prev parent reply other threads:[~2022-03-03 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:28 [PATCH 0/4] README: Fix setup, btrfs and distro info Gabriel Niebler
2022-03-03 13:28 ` Gabriel Niebler [this message]
2022-03-03 13:28 ` [PATCH 2/4] README: Adjust and add btrfs testing information Gabriel Niebler
2022-03-03 13:28 ` [PATCH 3/4] README: Add command to install required packages on SUSE Gabriel Niebler
2022-03-03 13:28 ` [PATCH 4/4] README: Fix indentation to be consistent Gabriel Niebler
2022-03-03 23:47 ` [PATCH 0/4] README: Fix setup, btrfs and distro info Dave Chinner
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=20220303132804.4151-2-gniebler@suse.com \
--to=gniebler@suse.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