Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
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