All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>,
	junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH] Support output ISO 8601 format dates
Date: Sun, 15 Jul 2007 15:14:51 -0700	[thread overview]
Message-ID: <7vveclco10.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070715212359.GB18293@efreet.light.src> (Jan Hudec's message of "Sun, 15 Jul 2007 23:23:59 +0200")

Jan Hudec <bulb@ucw.cz> writes:

> I apologise for nitpicking, but ISO 8601 (and RFC 3339) says separator between
> date and time is 'T' and there is no separator between time and timezone. So
> this should be
> ...
> ISO 8601 makes separators optional, so simple 4-digit timezone is OK.

My reading of 8601 was that it is allowed to drop [T] as long as
it is clear from the context by agreement between the parties
involved, although I admit the only copy I have handy is JIS
X0301 (2002), which is matching Japanese industrial standard
that consists of translation of ISO 8601 (2000) plus Japanese
"emperor's era" extensions.

  reply	other threads:[~2007-07-15 22:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 20:22 [PATCH] Support output ISO 8601 format dates Robin Rosenberg
2007-07-13 22:11 ` Junio C Hamano
2007-07-13 23:00   ` Robin Rosenberg
2007-07-14  6:42     ` [PATCH 1/2] Make show_rfc2822_date() just another date output format Junio C Hamano
2007-07-14  6:43     ` [PATCH 2/2] Wire new date formats to --date=<format> parser Junio C Hamano
2007-07-14  6:44       ` Jan-Benedict Glaw
2007-07-14  6:54         ` Junio C Hamano
2007-07-14 10:29       ` Robin Rosenberg
2007-07-14  6:49     ` [PATCH] Document new --date=<format> Junio C Hamano
2007-07-15 21:23 ` [PATCH] Support output ISO 8601 format dates Jan Hudec
2007-07-15 22:14   ` Junio C Hamano [this message]
2007-07-15 23:19   ` Robin Rosenberg
2007-07-15 23:57     ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vveclco10.fsf@assigned-by-dhcp.cox.net \
    --to=gitster@pobox.com \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=robin.rosenberg@dewire.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.