From: john+kernel+f2fs-devel--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH] Miscellaneous cleanup to README.
Date: Thu, 17 Dec 2020 04:14:57 -0500 [thread overview]
Message-ID: <20201217091457.7807-1-john+kernel+f2fs-devel@zlima12.com> (raw)
From: "John A. Leuenhagen" <john@zlima12.com>
---
README | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/README b/README
index 4ea3356..afe334f 100644
--- a/README
+++ b/README
@@ -1,8 +1,8 @@
-F2FS format utilility
+F2FS format utility
---------------------
-To use f2fs filesystem, you should format the storage partition
-with this utilility. Otherwise, you cannot mount f2fs.
+To use the f2fs filesystem, you should format the storage partition
+with this utility. Otherwise, you cannot mount f2fs.
Before compilation
------------------
@@ -17,7 +17,7 @@ You should install the following packages.
Initial compilation
-------------------
-Before compilation initially, autoconf/automake tools should be run.
+Before initial compilation, autoconf/automake tools should be run.
# ./autogen.sh
@@ -47,4 +47,4 @@ How to run by default
$ mkfs.f2fs -l [LABEL] $DEV
-For more mkfs options, see man page.
+For more mkfs options, see the man page.
--
2.26.2
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2020-12-17 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 9:14 john+kernel+f2fs-devel--- via Linux-f2fs-devel [this message]
2020-12-17 9:47 ` [f2fs-dev] [PATCH] Miscellaneous cleanup to README John A. Leuenhagen via Linux-f2fs-devel
2020-12-17 16:20 ` Jaegeuk Kim
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=20201217091457.7807-1-john+kernel+f2fs-devel@zlima12.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=john+kernel+f2fs-devel@zlima12.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;
as well as URLs for NNTP newsgroup(s).