[I repeat - PLEASE keep the list/bug-tracker in the loop, if you expect
anything to be done about your requests]
On 06/18/2010 12:18 PM, jari wrote:
> On 2010-06-18 11:43, Eric Blake wrote:
> | So, before anyone writes such a patch, what TIMESPEC options do you
> | propose would make the most sense for a new --iso-8601 command-line
> | option? And, seeing that RFC 3339 was derived from ISO 8601, do we even
> | need a new option, or is the existing behavior already present? In
> | other words, I'd still like to know what particular shortcuts you feel
> | are worth adding.
>
> I'm so used to 8601, so I dind't see the option --rfc-3339 from
> date(1) at first. Here are few commets:
>
>
> --rfc-3339=TIMESPEC
> output date and time in RFC 3339 format.
> TIMESPEC=`date', `seconds', or `ns' for date and time to
> the indicated precision. Date and time components are
> separated by a single space: 2006-08-07 12:34:56-06:00
>
> Additions to -rfc-3339 option
> -----------------------------
>
> Current:
>
> --rfc-3339="date" 2010-06-18
> --rfc-3339="seconds" 2010-06-18 21:08:05+03:00
>
> It would be nice to have also without timezone:
>
> --rfc-3339="time" 2010-06-18 21:08:00 (no TZ)
> --rfc-3339="word" 2010-06-18T21:08:00 (single word with
> seconds)
>
> New option --iso8601
> --------------------
>
> The 3339 is mostly unknown in the field, but almost everybody
> recognize 8601, so I'd like to suggest a shorthand for the most
> commonly used format (e,g, for log entries):
>
> --iso8601
>
> That would be same as the long option:
>
> --rfc-3339="time"
>
> Perhaps also "memory friendly":
>
> --iso8601="tz"
>
> Which would be equivalent for:
>
> --rfc-3339="seconds"
>
> Jari
>
>
>
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc Description: OpenPGP digital signature