From: Karel Zak <kzak@redhat.com>
To: Jean-Philippe ROMAIN <jean-philippe.romain@st.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] dmesg: correct "-n, --console-level level" example in manual page
Date: Mon, 17 Dec 2018 10:48:39 +0100 [thread overview]
Message-ID: <20181217094839.tr2datbuqyjze54v@ws.net.home> (raw)
In-Reply-To: <1545035454-30986-1-git-send-email-jean-philippe.romain@st.com>
On Mon, Dec 17, 2018 at 09:30:54AM +0100, Jean-Philippe ROMAIN wrote:
> When providing an abbreviation of the level name with the option "-n, --console-level level",
> it corresponds to the level (included) up to which messages are displayed on the console.
> If a level number is given, this level is excluded.
>
> So in the given example, "-n 1" is equivalent to "-n emerg".
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2018-12-17 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 8:30 [PATCH] dmesg: correct "-n, --console-level level" example in manual page Jean-Philippe ROMAIN
2018-12-17 9:48 ` Karel Zak [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=20181217094839.tr2datbuqyjze54v@ws.net.home \
--to=kzak@redhat.com \
--cc=jean-philippe.romain@st.com \
--cc=util-linux@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 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).