From: Kinglong Mee <kinglongmee@gmail.com>
To: Eryu Guan <eguan@redhat.com>, fstests@vger.kernel.org
Cc: sandeen@redhat.com, Kinglong Mee <kinglongmee@gmail.com>
Subject: [PATCH] README: fix the typo of local.config.example
Date: Wed, 18 Jan 2017 18:33:03 +0800 [thread overview]
Message-ID: <83ca1aaa-7f30-bece-87e1-4faab1ebdc72@gmail.com> (raw)
Commit b7d908a0e8eb "README: document Fedora, RHEL, and
CentOS dependencies" adds a typo of local.config.example
to config.local.example, fix it.
Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 400e902..f788e71 100644
--- a/README
+++ b/README
@@ -63,7 +63,7 @@ Preparing system for tests (IRIX and Linux):
- setup your environment
Quick start:
- - copy config.local.example to config.local and edit as needed
+ - copy local.config.example to local.config and edit as needed
Or:
- setenv TEST_DEV "device containing TEST PARTITION"
- setenv TEST_DIR "mount point of TEST PARTITION"
--
2.9.3
next reply other threads:[~2017-01-18 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:33 Kinglong Mee [this message]
2017-01-18 10:51 ` [PATCH] README: fix the typo of local.config.example Kinglong Mee
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=83ca1aaa-7f30-bece-87e1-4faab1ebdc72@gmail.com \
--to=kinglongmee@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=sandeen@redhat.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