From: Eric Biggers <ebiggers@google.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: [xfstests-bld PATCH] util/get-config: stop sourcing deprecated config files
Date: Thu, 5 Apr 2018 14:20:10 -0700 [thread overview]
Message-ID: <20180405212010.132258-1-ebiggers@google.com> (raw)
Stop sourcing configs from the deprecated locations $KVM_CONFIG or
kvm-xfstests/config.custom, in preference to the locations in
~/.config/. kvm-xfstests and gce-xfstests have been warning when
sourcing from the deprecated locations for almost a year now, so it's
unlikely that anyone is using them anymore.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
kvm-xfstests/util/get-config | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/kvm-xfstests/util/get-config b/kvm-xfstests/util/get-config
index 4baf494..894bf3b 100644
--- a/kvm-xfstests/util/get-config
+++ b/kvm-xfstests/util/get-config
@@ -48,21 +48,6 @@ then
rm "$tmpfile"
unset tmpfile
fi
-
if test -n "$GCE_ACCOUNT" -a -f "$DIR/config-$GCE_ACCOUNT" ; then
. "$DIR/config-$GCE_ACCOUNT"
-elif test -f $DIR/config.custom ; then
-# Else, source kvm-xfstests/config.custom if present (deprecated)
- echo -e 1>&2 "Warning: use of kvm-xfstests/config.custom is deprecated." \
- "Move your settings\n into ~/.config/kvm-xfstests," \
- "~/.config/gce-xfstests,\n ~/.config/android-xfstests," \
- "and/or ~/.config/xfstests-common"
- . $DIR/config.custom
-fi
-
-# Source $KVM_CONFIG if present (deprecated)
-if test -n "$KVM_CONFIG" -a -f "$KVM_CONFIG"; then
- echo -e 1>&2 "Warning: use of \$KVM_CONFIG is deprecated." \
- "Move your settings into\n ~/.config/kvm-xfstests"
- . $KVM_CONFIG
fi
--
2.17.0.484.g0c8726318c-goog
next reply other threads:[~2018-04-05 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 21:20 Eric Biggers [this message]
2018-04-06 13:26 ` [xfstests-bld PATCH] util/get-config: stop sourcing deprecated config files Theodore Y. Ts'o
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=20180405212010.132258-1-ebiggers@google.com \
--to=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=tytso@mit.edu \
/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