From: Eric Biggers <ebiggers@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH] fsck.f2fs: use clearer info message for -a option
Date: Mon, 4 Sep 2023 17:38:02 -0700 [thread overview]
Message-ID: <20230905003802.333176-1-ebiggers@kernel.org> (raw)
From: Eric Biggers <ebiggers@google.com>
The message "Info: Fix the reported corruption" makes people think that
fsck has detected filesystem corruption. Replace this message with
"Info: Automatic fix mode enabled" which is more accurate.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
fsck/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fsck/main.c b/fsck/main.c
index 3690c74..dd8643c 100644
--- a/fsck/main.c
+++ b/fsck/main.c
@@ -263,7 +263,7 @@ void f2fs_parse_options(int argc, char *argv[])
break;
case 'a':
c.auto_fix = 1;
- MSG(0, "Info: Fix the reported corruption.\n");
+ MSG(0, "Info: Automatic fix mode enabled.\n");
break;
case 'c':
c.cache_config.num_cache_entry = atoi(optarg);
base-commit: b15b6cc56ac7764be17acbdbf96448f388992adc
--
2.42.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2023-09-05 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230905003802.333176-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.