Re: Bug report: Author/Commit date in ISO 8601 format

From: Jeff King <peff@peff.net>
Date: Aug 26, 2014, 14:22 UTC
Message-ID: <20140826142203.GA31205@peff.net>
In-Reply-To: <F8DE5B94F596455FA56956B8A865EC73@black>

On Tue, Aug 26, 2014 at 10:10:33AM -0400, Jason Pyeron wrote:

Show 10 quoted lines

> > But I am not sure that "omitted" means "can be replaced with a space".
> > And while you can define "by mutual agreement" as "git defines the
> > format, so any consumers agree to it" that is not necessarily 
> > useful to
> > somebody who wants to feed the result to an iso8601 parser 
> > that does not
> > know or care about git (i.e., it shoves the conversion work onto the
> > person in the middle).
> 
> Omitted /T?/ does not mean replaced with another character.

I would agree. But that is the argument made in the thread I linked earlier.

I do not think there is much point in re-opening the argument, though. Whatever git generates, changing the output would probably cause a lot of pain. We are likely better off adding a new, "real" iso8601 format option (we can even deprecate the old one, or slate it for switching, but we would need a notification period).

-Peff