GNU bug report logs - #6132
date: --rfc-3339=TIMESPEC option doesn't print 'T'

Previous Next

Package: coreutils;

Reported by: "F. Alexander Njemz" <f.alexander.njemz <at> googlemail.com>

Date: Fri, 7 May 2010 15:08:01 UTC

Severity: normal

Tags: notabug

Merged with 39693

Full log


Message #11 received at 6132 <at> debbugs.gnu.org (full text, mbox):

From: "F. Alexander Njemz" <f.alexander.njemz <at> googlemail.com>
To: Eric Blake <eblake <at> redhat.com>
Cc: 6132 <at> debbugs.gnu.org,
	"F. Alexander Njemz" <f.alexander.njemz <at> googlemail.com>
Subject: Re: bug#6132: bug in date: --rfc-3339=TIMESPEC option doesn't print
	'T'
Date: Sat, 08 May 2010 10:33:08 +0200
[Message part 1 (text/plain, inline)]
On 05/07/2010 05:55 PM, Eric Blake wrote:
> On 05/07/2010 07:25 AM, F. Alexander Njemz wrote:
>    
>> Hi,
>>
>> as evidenced here [1] the slightly ambiguous wording in the RFC 3339 [2]
>> seems to be the reason that the date utility using the
>> --rfc3339=TIMESPEC switch formats the date with a space instead of a 'T'.
>>
>> I was confused as well, so I took the liberty to mail the authors of the
>> RFC in question. I attached the reply from Mr. Klyne.
>>
>> There is also a patch attached.
>>      
> Thanks for the report, and also for the patch.  However, I'm reluctant
> to create a date format that we cannot then reparse.  So before we apply
> this patch, we would first need a patch to gnulib's getdate.y that
> allows parsing of an rfc3339 style with a 'T' instead of a space.
>
>    


Hi Mr. Blake, hi mailing list,

I'm looking into getdate.y.
Mr. Newman has replied as well (see attachment).

I don't think Mr. Newman's mail applies to the date command, since IMHO 
date returns a
single field.

What do you think?

Regards,

F. Alexander Njemz
[rfc3339 is the T mandatory?.eml (message/rfc822, attachment)]

This bug report was last modified 5 years and 124 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.