On 04/19/2013 12:47 PM, Donald Berry wrote:
> Are there any plans to reject invalid strings?
Not as far as I know.
On 04/18/2013 01:24 PM, Donald Berry wrote:
> If an invalid TZ argument is passed to /bin/date, it silently fails but
> prints the UTC result:
> [dberry@dberry ~]$ TZ=EDT date -d @0
> Thu Jan 1 00:00:00 EDT 1970
> [dberry@dberry ~]$ TZ=foo date -d @0
> Thu Jan 1 00:00:00 foo 1970
>
> It works c
On Friday 19 April 2013 15:47:46 Donald Berry wrote:
> Yes, date/GNU accepts whatever TZ string you pass it without error, but
> this leads to very confusing results.
Paul said the "GNU system", not "GNU/date". coreutils doesn't parse the TZ
env var, the C library does. similarly, the date progr
13 5:29:33 PM
Subject: Re: bug#14229: invalid TZ and /bin/date
On 04/18/13 13:24, Donald Berry wrote:
> If an invalid TZ argument is passed to /bin/date,
> it silently fails but prints the UTC result
In the GNU system there is no such thing
as an invalid TZ string. Every TZ string has
some int
On 04/18/13 13:24, Donald Berry wrote:
> If an invalid TZ argument is passed to /bin/date,
> it silently fails but prints the UTC result
In the GNU system there is no such thing
as an invalid TZ string. Every TZ string has
some interpretation (typically as UTC).
This is true not just for /bin/dat
If an invalid TZ argument is passed to /bin/date, it silently fails but prints
the UTC result:
[dberry@dberry ~]$ TZ=EDT date -d @0
Thu Jan 1 00:00:00 EDT 1970
[dberry@dberry ~]$ TZ=foo date -d @0
Thu Jan 1 00:00:00 foo 1970
It works correctly if using no argument or a valid argument:
[dberry@d
