util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@justemail.net>
To: Karel Zak <kzak@redhat.com>
Cc: JWP <elseifthen@gmx.com>, "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: [PATCH 0/5] hwclock: clean up messages
Date: Fri, 24 Oct 2014 13:48:33 +0200	[thread overview]
Message-ID: <1414151313.843395.182838257.3685FB42@webmail.messagingengine.com> (raw)
In-Reply-To: <20141024110803.GB10134@x2.net.home>


On Fri, Oct 24, 2014, at 13:08, Karel Zak wrote:
> On Thu, Oct 23, 2014 at 10:44:31PM -0400, JWP wrote:
> > This patch set cleans up various message output.
> > It contains cosmetic changes only.
> > 
> > J William Piggott (5):
> >   hwclock: Remove newline from 'date' debug output
> >   hwclock: clean up message periods/full stops
> >   hwclock: add message line breaks
> >   hwclock: Fix --date debug messages
> >   hwclock: version prints out of order
> 
> I'm going to merge these patches,

Please no.  Not the mere period and linebreak changes.

> but as a long term solution it would
> better to use include/debug.h stuff (see for example
> misc-utils/whereis.c or libmount/src/init.c).

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.

Benno

-- 
http://www.fastmail.fm - Does exactly what it says on the tin


  parent reply	other threads:[~2014-10-24 11:48 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 [this message]
2014-10-24 12:18     ` Karel Zak
2014-10-24 12:22     ` JWP
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=1414151313.843395.182838257.3685FB42@webmail.messagingengine.com \
    --to=bensberg@justemail.net \
    --cc=elseifthen@gmx.com \
    --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 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).