From: "Theodore Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsck: map PROMPT_* values to prompt messages
Date: Mon, 2 May 2022 23:31:17 -0400 [thread overview]
Message-ID: <165154867067.863734.3098529501886543374.b4-ty@mit.edu> (raw)
In-Reply-To: <20211208075112.85649-1-adilger@dilger.ca>
On Wed, 8 Dec 2021 00:51:12 -0700, Andreas Dilger wrote:
> It isn't totally clear when searching the code for PROMPT_*
> constants from problem codes where these messages come from.
> Similarly, there isn't a direct mapping from the prompt string
> to the constant.
>
> Add comments that make this mapping more clear.
>
> [...]
Applied, thanks!
[1/1] e2fsck: map PROMPT_* values to prompt messages
commit: c1bd25333e8986b081b82a8eb8c9173a0c7480af
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2022-05-03 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 7:51 [PATCH] e2fsck: map PROMPT_* values to prompt messages Andreas Dilger
2021-12-08 16:42 ` Darrick J. Wong
2021-12-09 21:55 ` Andreas Dilger
2021-12-11 0:51 ` Darrick J. Wong
2022-02-28 23:58 ` Andreas Dilger
2022-05-03 3:31 ` Theodore Ts'o [this message]
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=165154867067.863734.3098529501886543374.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@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 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.