Re: [PATCH 2/5] hwclock: clean up message periods/full stops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 24, 2014 at 10:58:07PM +0200, Benno Schulenberg wrote:
> 
> On Fri, Oct 24, 2014, at 18:07, JWP wrote:
> > So what is the util-linux position on message punctuation in general, and
> > line termination specifically?  The documentation seem to imply not using any.
> 
> The current situation is a mess.  And the documentation does not say
> anything about what error messages, status reports, and imperatives

I don't think so, but it would be nice to have
Documentation/howto-messages.txt.

> to the user should look like.  The general style seems to be:
> 
> 1) Error messages (anything that is preceded by the program name
> followed by a colon and a space, in thise case "hwclock: ") start with
> a lowercase letter and do not end in a period, nor use any period.

The preferred way to print error and warning messages is err() and
warn() (or errx() and warnx()). 

> 2) Status reports and imperatives to the user use full sentences:
> they start with a capital letter and end in a period.

yep.

    Karel

-- 
 Karel Zak  <kzak@xxxxxxxxxx>
 http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux