GNU bug report logs - #24077
VS: bug in MAN page for data command

Previous Next

Full log

View this message in rfc822 format

From: Pádraig Brady <P <at> draigBrady.com>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>, 24077-done <at> debbugs.gnu.org, eggert <at> cs.ucla.edu, lsa <at> logos.dk
Subject: bug#24077: VS: bug in MAN page for data command
Date: Wed, 27 Jul 2016 10:13:42 +0100

[Message part 1 (text/plain, inline)]

On 27/07/16 09:20, Bernhard Voelker wrote:
> On 07/27/2016 09:07 AM, Paul Eggert wrote:
>> On 07/26/2016 09:13 AM, Lars Issing Sauer wrote:
>>>   According to the description "%M" is minutes and "%m" is month... but
>>>   the command takes "%M" as month and "%m" as minutes ;)
>>
>> Sorry, I don't see any bug here. "date +%M" outputs the current number of minutes
>> past the hour, and "date +%m" outputs the current month number, and that is what is documented.
> 
> Hi Paul,
> 
> I think it's regarding the MM vs. mm in the usage string:
> 
>   $ src/date --help | grep MM
>     or:  src/date [-u|--utc|--universal] [MMDDhhmm[[CC]YY][.ss]]
> __________________________________________^^____^^
> 
>   $ src/date -u 072710132016
>   src/date: cannot set date: Operation not permitted
>   Wed Jul 27 10:13:00 UTC 2016
> 
> The MM/mm here is inconsistent compared to the %M/%m modifiers.
> 
> Usage | % mod | meaning
> ------+-------+--------
>  MM   | %m    | month
>  mm   | %M    | minute
> 
> Do you agree?

Yes it's more consistent to match this input representation
with the output +FORMATs.  I.E. use: [mmddHHMM[[CC]yy][.SS]]
It's more natural to use uppercase for larger quantities,
but being consistent with +FORMAT trumps that IMHO.

Fixed in the attached.

thanks
Pádraig

[date-synopsis.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.