[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in date command
From: |
Bob Proulx |
Subject: |
Re: Bug in date command |
Date: |
Wed, 7 Jan 2009 21:00:09 -0700 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Eric Blake wrote:
> A couple of nits:
>
> "The parsing of dates with date --date=STRING is a GNU extension and not
> covered by any standards beyond those to which GNU holds itself." Not
> entirely true any longer, now that POSIX 2008 requires that 'touch -d
> STRING' parse a limited format of ISO dates, and we implement that with
> the same date parsing engine as our (true GNU extension) 'date -d'.
Good point. I added the following to the previous description.
However @command{touch -d STRING} is defined by POSIX and is
implemented with the same date string parsing code. Therefore you
can expect that similar rules will apply to both.
> "The %Y and %U options work in combination." To be fair, we should state
> that the %Y and your choice of %U/%W work in combination (%W if you want
> Monday, %U if you want Sunday as the first day of the week).
As per your suggestion I have added discussion of %W too.
The @option{%Y} and @option{%U} or @option{%W} options work in
combination. (Use @option{%U} for weeks starting with Sunday or
@option{%W} for weeks starting with Monday.) The ISO @option{%G} and
@option{%V} options work in combination. Mixing them up creates
confusion. Instead use @option{%Y} and @option{%U}/@option{%W}
together or use @option{%G} and @option{%V} together.
Bob