Re: bug in date: --rfc-3339=seconds and --rfc-3339=ns options do *not* output timestamps in RFC 3339 format

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Romain Lenglet on 5/3/2006 12:47 AM:
> Hi,
> 
> RFC 3339 makes it *mandatory* to separate the date and time with 
> a "T" in timestamps. Cf. section 5.6 of RFC 3339, describing the 
> timestamp syntax in ABNF:
> 
> date-time       = full-date "T" full-time

Hmm.  Are you sure about that?  My understanding was that we deprecated -I
for being non-compliant with ISO 8601 because RFC 3339 explicitly requires
that the 'T' NOT appear in the date.  Reread section 5.6 in RFC 3339,
which permits implementations to avoid 'T'.  See the threads here, where
the --rfc-3339 option was discussed, and later added:

http://lists.gnu.org/archive/html/bug-coreutils/2005-07/msg00186.html
http://lists.gnu.org/archive/html/bug-coreutils/2005-09/msg00056.html

If you need the "T", for now you can rely on the undocumented --iso-8601
option.

> 
> I am not providing you a patch, since I don't want to go through 
> the administrative burden of copyright transfer for so little, 
> but here are the correct date formats for the RFC 3339 options:

If the patch is less than 10 lines, it is considered trivial and can be
applied without copyright assignment.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEWKgU84KuGfSFAYARAhceAJ9xoPDZHzWW8wm3C/t+xCQFu040OwCfbX3U
6E7EyVWfclsCg3ht54jLhlk=
=NMt2
-----END PGP SIGNATURE-----