Peff is right, I did not think of backwards compatibility issues. I believe a new option like "iso-strict" as he suggested will do the trick (and I'm probably not the only one to appreciate its implementation...).



Am 26.08.2014 um 15:06 schrieb Jeff King:
On Tue, Aug 26, 2014 at 09:29:44AM +0200, Oliver Busch wrote:

I encountered the following problem: When using the date formatting option
ISO (either by setting --date=iso or using format:%ci for the committer
date), the output is formatted like this:

2014-08-25 17:49:43 +0200

But according to ISO 8601, should be formatted like this (see

Yeah, it is not strictly ISO but more ISO-like (to further add
confusion, it is mostly RFC3339, which claims to be a "profile of
ISO8601". But we don't follow the timezone conventions there. Yeesh).

Interestingly, this actually came up when the feature was added:

but there was some discussion of ISO8601's weird phrasing of "T" being

I therefore suggest to adapt the output when using --date=iso or
format:%ci to comply 100% with the ISO 8601 specs, or at least change
documentation to say the output is only "ISO-like".
I think changing the output at this point would cause backwards
compatibility problems (not to mention that it's a lot less readable for

Patches welcome for a documentation update. I also think something like
--date=iso8601-strict might make sense for the case of feeding the
result to another parser.



Oliver Busch, M.Eng.

Airport Research Center GmbH
Bismarckstra├če 61
52066 Aachen

Phone: +49 241 16843-161
Fax: +49 241 16843-19

Register Court: Amtsgericht Aachen HRB 7313
Ust-Id-No.: DE196450052

Managing Directors:
Dipl.-Ing. Tom Alexander Heuer

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to