Bug#569174: [PATCH] Correction of RFC number for date format -- bug #569174.
On Tue, Jun 01, 2010 at 10:47:18AM +0900, Charles Plessy wrote:
> RFC 822 dates use only two digits for the years, but Debian changelogs
> described by this paragraph (§4.4 in Policy 3.8.4) use four digits. This patch
> replaces the RFC 822 by its latest evolution, RFC 5322, that specifies a date
> format suitable for Debian changelogs.
> ---
> policy.sgml | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/policy.sgml b/policy.sgml
> index d16df70..7e2365e 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -1610,7 +1610,7 @@
> </p>
>
> <p>
> - The <var>date</var> must be in RFC822 format<footnote>
> + The <var>date</var> must be in RFC5322 format<footnote>
> This is generated by <tt>date -R</tt>.
> </footnote>; it must include the time zone specified
> numerically, with the time zone name or abbreviation
> --
> 1.6.5.7
What is the diffrence between RFC5322 and RFC2822 time format ?
RFC 5322 was only released in 2008, so the standard that packages
actually follow is clearly RFC2822.
I would prefer if we keep a reference to RFC2822 because is is
more well known than RFC5322
The 'date' utility denotes this format under 'RFC 2822':
The option is named --rfc-2822 and the documentation list
RFC 2822.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: