From: Timo Hirvonen <tihirvon@gmail.com>
To: git@vger.kernel.org
Subject: git-format-patch Date header
Date: Sun, 8 Jan 2006 16:40:38 +0200 [thread overview]
Message-ID: <20060108164038.89e4439f.tihirvon@gmail.com> (raw)
In-Reply-To: <20060108141457.8C4E85BE8F@nox.op5.se>
git-format-patch uses "date '+%s %z'" format for the Date header.
Sylpheed does not understand this format. How common this convention
is? Should we change git-format-patch to use more standard date format?
OTOH, I like the %s format because it is so simple and easy to parse :)
--
http://onion.dynserv.net/~timo/
next prev parent reply other threads:[~2006-01-08 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 14:15 [PATCH] .gitignore git-describe Andreas Ericsson
2006-01-08 14:40 ` Timo Hirvonen [this message]
2006-01-08 15:21 ` git-format-patch Date header Andreas Ericsson
2006-01-08 15:37 ` Timo Hirvonen
2006-01-08 15:44 ` Andreas Ericsson
2006-01-08 22:05 ` H. Peter Anvin
2006-01-08 23:30 ` Andreas Ericsson
2006-01-09 6:11 ` Linus Torvalds
2006-01-08 14:01 ` [PATCH] format-patch: Use --mbox by default Andreas Ericsson
2006-01-08 20:28 ` Junio C Hamano
2006-01-09 2:01 ` Andreas Ericsson
2006-01-08 22:14 ` H. Peter Anvin
2006-01-09 2:05 ` Andreas Ericsson
2006-01-13 23:56 ` [PATCH] format-patch: always --mbox and show sane Date: Junio C Hamano
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=20060108164038.89e4439f.tihirvon@gmail.com \
--to=tihirvon@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).