From: Linus Torvalds <torvalds@osdl.org>
To: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
Cc: git@vger.kernel.org
Subject: Re: Parseable commit header
Date: Sun, 17 Apr 2005 08:57:43 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0504170856470.7211@ppc970.osdl.org> (raw)
In-Reply-To: <20050417062236.GA3261@scotty.home>
On Sun, 17 Apr 2005, Stefan-W. Hahn wrote:
>
> 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.
Actually, it is. The commit stuff removes all special characters from the
strings, so '<' and '>' around the email do indeed act as delimiters, and
cannot exist anywhere else.
Linus
next prev parent reply other threads:[~2005-04-17 15:52 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 [this message]
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=Pine.LNX.4.58.0504170856470.7211@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=stefan.hahn@s-hahn.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