git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Oliver Busch <oliver.busch@arc-aachen.de>, git@vger.kernel.org
Subject: Re: Bug report: Author/Commit date in ISO 8601 format
Date: Tue, 26 Aug 2014 10:22:03 -0400	[thread overview]
Message-ID: <20140826142203.GA31205@peff.net> (raw)
In-Reply-To: <F8DE5B94F596455FA56956B8A865EC73@black>

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

> > 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

  reply	other threads:[~2014-08-26 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  7:29 Bug report: Author/Commit date in ISO 8601 format Oliver Busch
2014-08-26 13:06 ` Jeff King
2014-08-26 13:14   ` Oliver Busch
2014-08-26 13:19   ` Oliver Busch
2014-08-26 13:33     ` Jeff King
2014-08-26 14:10       ` Jason Pyeron
2014-08-26 14:22         ` Jeff King [this message]
     [not found]           ` <CANgJU+UifjMJPcmC28-SrZOEUR45qQQfdM_rf-HHtkfBAMEyRw@mail.gmail.com>
2014-08-27  7:15             ` Oliver Busch

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=20140826142203.GA31205@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=oliver.busch@arc-aachen.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).