retitle 31634 822-date is misleading, obsolete, and should be removed severity 31634 important thanks After doing some research, I discovered that the 822-date application does not actually even output dates compliant with <urn:ietf:rfc:822>. A later RFC, <urn:ietf:rfc:1123>, made modifications (almost all of which I am too tired to parse) to the date format. However, from what I am able to tell (and once again, I am quite tired), it did not obsolete <urn:ietf:rfc:822>. In April 2001, <urn:ietf:rfc:2822> was born, which finally obsoleted <urn:ietf:rfc:822> once and for all. Along with it, of course, came the <urn:ietf:rfc:2822> date format, which can be generated by the date application by invoking it with the --rfc-2822 option. (The date application is part of coreutils and therefore should be on every system.) I suggest that all references to 822-date be replaced with references to date --rfc-2822 and that 822-date be removed as soon as possible.
Description: This is a digitally signed message part