From: JWP <elseifthen@gmx.com>
To: Benno Schulenberg <bensberg@justemail.net>, Karel Zak <kzak@redhat.com>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 0/5] hwclock: clean up messages
Date: Fri, 24 Oct 2014 08:22:47 -0400 [thread overview]
Message-ID: <544A4497.3010203@gmx.com> (raw)
In-Reply-To: <1414151313.843395.182838257.3685FB42@webmail.messagingengine.com>
On 10/24/2014 07:48 AM, Benno Schulenberg wrote:
>
> On Fri, Oct 24, 2014, at 13:08, Karel Zak wrote:
>> On Thu, Oct 23, 2014 at 10:44:31PM -0400, JWP wrote:
>
> In hwclock the "debug" messages are gettextized, because in fact
> they are verbose messages to help the user understand what hwclock
> is doing. They are not meant to find programming errors in hwclock;
> if that were the case, they wouldn't be gettextized, because a
> programmer needs to be able to read an write English anyway.
I would agree that it should have been named --verbose. However, I
have not suggested it because of Util-linux guidelines:
>From util-linux//Documentation/howto-usage-function.txt
"The rule of thumb with other options is that once they exist, you may
not change them, nor change how they work, nor remove them."
The --debug output is useful for testing and debugging, as I have
used it as such many times.
>
> Benno
>
next prev parent reply other threads:[~2014-10-24 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 2:44 [PATCH 0/5] hwclock: clean up messages JWP
2014-10-24 11:08 ` Karel Zak
2014-10-24 11:15 ` JWP
2014-10-24 11:48 ` Benno Schulenberg
2014-10-24 12:18 ` Karel Zak
2014-10-24 12:22 ` JWP [this message]
2014-10-24 13:18 ` Benno Schulenberg
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=544A4497.3010203@gmx.com \
--to=elseifthen@gmx.com \
--cc=bensberg@justemail.net \
--cc=kzak@redhat.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 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.