From: Gabriel Niebler <gniebler@suse.com>
To: fstests@vger.kernel.org
Cc: Gabriel Niebler <gniebler@suse.com>
Subject: [PATCH 4/4] README: Fix indentation to be consistent
Date: Thu, 3 Mar 2022 14:28:04 +0100 [thread overview]
Message-ID: <20220303132804.4151-5-gniebler@suse.com> (raw)
In-Reply-To: <20220303132804.4151-1-gniebler@suse.com>
Fix two lines that were indented with TABS when everything around them uses spaces
Signed-off-by: Gabriel Niebler <gniebler@suse.com>
---
README | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README b/README
index 657fb2f6..f43a5a8c 100644
--- a/README
+++ b/README
@@ -83,9 +83,9 @@ Preparing system for tests:
- setenv TAPE_DEV "tape device for testing xfsdump"
- setenv RMT_TAPE_DEV "remote tape device for testing xfsdump"
- setenv RMT_IRIXTAPE_DEV "remote IRIX tape device for testing xfsdump"
- - setenv SCRATCH_LOGDEV "device for scratch-fs external log"
+ - setenv SCRATCH_LOGDEV "device for scratch-fs external log"
- setenv SCRATCH_RTDEV "device for scratch-fs realtime data"
- - setenv TEST_LOGDEV "device for test-fs external log"
+ - setenv TEST_LOGDEV "device for test-fs external log"
- setenv TEST_RTDEV "device for test-fs realtime data"
- if TEST_LOGDEV and/or TEST_RTDEV, these will always be used.
- if SCRATCH_LOGDEV and/or SCRATCH_RTDEV, the USE_EXTERNAL
--
2.35.1
next prev parent reply other threads:[~2022-03-03 13:29 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 ` [PATCH 1/4] README: Fix environment setup quick start Gabriel Niebler
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 ` Gabriel Niebler [this message]
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-5-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