From: "David A. Wheeler" <dwheeler@dwheeler•com>
To: "Stefan-W. Hahn" <stefan.hahn@s-hahn•de>
Cc: git@vger•kernel.org
Subject: Re: Parseable commit header
Date: Sun, 17 Apr 2005 12:49:24 -0400 [thread overview]
Message-ID: <42629394.1090804@dwheeler.com> (raw)
In-Reply-To: <20050417062236.GA3261@scotty.home>
Stefan-W. Hahn wrote:
> Hi,
>
> after playing a while with git-pasky it is a crap to interpret the date of
> commit logs. Though it was a good idea to put the date in a parseable format
> (seconds since), but the format of the commit itself is not good parseable.
> Should be:
...
> Committer-Dater: 1113684324 +0200
I'm probably coming in late to the game, but exactly
why is seconds-since-epoch format used instead of a format
more easily understood by humans? Yes, I know tools
can easily convert that, but you're already using an ASCII format;
why not just record it in a format that's easily eyeballed like ISO's
yyyymmddThhmmss [timezone]? E.G.:
20050417T171520 +0200
or some such? I'm SURE that people will mention things
like "the patch I posted on April 17, 2005", and having the
patch format record times that way, directly, would be convenient
to the poor slobs^H^H^H^H^H developers who come later.
Yes, a tool can handle the conversion, but choosing formats
so a tool is unneeded for simple stuff is often better....!
--- David A. Wheeler
prev parent reply other threads:[~2005-04-17 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 6:22 Parseable commit header Stefan-W. Hahn
2005-04-17 15:57 ` Linus Torvalds
2005-04-17 16:49 ` David A. Wheeler [this message]
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=42629394.1090804@dwheeler.com \
--to=dwheeler@dwheeler$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=stefan.hahn@s-hahn$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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