Git development
 help / color / mirror / Atom feed
From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: git@vger.kernel.org
Subject: Parseable commit header
Date: Sun, 17 Apr 2005 08:22:36 +0200	[thread overview]
Message-ID: <20050417062236.GA3261@scotty.home> (raw)

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.

For easy converting the commit log header in readable format it should be in
another format, perhaps like mail header: 
- Every field should start al column zero wih filedname end up with a colon.
- Every fieldname starts with an upcase letter.
- The dates of author and committer should be fields of it own.
- The commit message itself is seperated by a blank line.


Example current log entry:

commit fe077e9d16819b72c275ea40b254f22b4d236f8b
tree 98b57b0310e0e2309fe4a6c24a6abea31a4d6c6d
parent f0adb6cf1bf603537afff5cf26b90e81321db225
author Petr Baudis <pasky@ucw.cz> 1113684324 +0200
committer Petr Baudis <xpasky@machine> 1113684324 +0200

s/me/commit/ in git log output.


Should be:

Commit: fe077e9d16819b72c275ea40b254f22b4d236f8b
Tree: 98b57b0310e0e2309fe4a6c24a6abea31a4d6c6d
Parent: f0adb6cf1bf603537afff5cf26b90e81321db225
Author: Petr Baudis <pasky@ucw.cz> 
Author-Date: 1113684324 +0200
Committer: Petr Baudis <xpasky@machine> 
Committer-Dater: 1113684324 +0200

s/me/commit/ in git log output.


This date entries are now easy parseable and convertable.

- Stefan

-- 
Stefan-W. Hahn                          It is easy to make things.
/ mailto:stefan.hahn@s-hahn.de /        It is hard to make things simple.			


             reply	other threads:[~2005-04-17  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17  6:22 Stefan-W. Hahn [this message]
2005-04-17 15:57 ` Parseable commit header Linus Torvalds
2005-04-17 16:49 ` David A. Wheeler

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=20050417062236.GA3261@scotty.home \
    --to=stefan.hahn@s-hahn.de \
    --cc=git@vger.kernel.org \
    /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