From: Andreas Ericsson <ae@op5.se>
To: Timo Hirvonen <tihirvon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-format-patch Date header
Date: Sun, 08 Jan 2006 16:44:41 +0100 [thread overview]
Message-ID: <43C13369.4090809@op5.se> (raw)
In-Reply-To: <20060108173736.199df297.tihirvon@gmail.com>
Timo Hirvonen wrote:
> On Sun, 08 Jan 2006 16:21:13 +0100
> Andreas Ericsson <ae@op5.se> wrote:
>
>
>>Timo Hirvonen wrote:
>>
>>>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 :)
>>>
>>
>>Actually, that's what's printed in the commit message, so any change
>>would have to be put there and that would break backwards compatibility
>>for new tools that might want to use it.
>
>
> So fixing Sylpheed (and maybe other email clients too) is the right
> solution...
>
Nopes. In this case fixing my home-hacked git-send-patch script is the
right thing to do. git-format-patch has always printed that format,
though, so the error lies with me and the patch I sent. I shall have to
re-visit it after reading rfc 822 a bit more closely.
>
>>On an unrelated note, please don't start a new thread by replying to an
>>old message. It's very confusing to follow and people may not see your
>>message. This time it was doubly so because the next mail in my inbox is
>>a patch for git-format-patch, to which I thought you replied.
>
>
> Sorry. I replied to your message because it was the message having Date
> header in the "%s %z" format.
>
I just noticed. Thanks, and sorry.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-01-08 15:44 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 ` git-format-patch Date header Timo Hirvonen
2006-01-08 15:21 ` Andreas Ericsson
2006-01-08 15:37 ` Timo Hirvonen
2006-01-08 15:44 ` Andreas Ericsson [this message]
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=43C13369.4090809@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=tihirvon@gmail.com \
/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).