From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] format-patch: Use --mbox by default.
Date: Mon, 09 Jan 2006 03:01:30 +0100 [thread overview]
Message-ID: <43C1C3FA.8070609@op5.se> (raw)
In-Reply-To: <7vhd8ezcol.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andreas Ericsson <ae@op5.se> writes:
>
>
>>This patch enables a slightly modified and more correct --mbox
>>output by default. The --date, --author and --mbox options
>>are obsoleted and removed.
>
>
> I always use format-patch with -k -m (or -k --stdout), so I have
> no objections to making --mbox the default. I do not think
> anybody uses --date or --author in their scripts, but removing
> the --mbox option _might_ break things for people's scripts.
> Maybe it is worthwhile to keep it as a no-op option for a while.
>
The reworked patch (which works for sending patches to myself, so far),
prints a warning to stderr that a deprecated option is used and then
silently ignores it.
>
>>The patches generated also had bad mail headers for sendmail (of
>>postfix 2.2.2 at least) to use directly (From: line must be on top,
>>Subject: last of header),...
>
>
> I do not think RFC2822 specifies that. See "3.6 Field
> definitions", third paragraph, first two sentences.
>
> In that sense, technically they are not "bad mail headers", but
> at the same time, since it is valid in any order, if _one_
> popular MTA is unconfortable with a particular ordering, we
> could order things differently to make it happier (mind you,
> this would not work for more than one such broken MTAs).
>
The only thing I've seen break is if Subject: is placed on top. It's
easier, script-wise, to put it last and that seems to work with qmail
and postfix both.
> Another thing I've been considering is to handle UTF-8 (or
> i18n.commitencoding in general) a bit better. We currently do
> not have Content-Type: header, so if you pipe the output to
> "am", it must be invoked without "-u" to make sure that it takes
> things as-is ("am -u" assumes things are in latin1 without
> Content-Type:). If we start to tackle that issue, we might also
> want to do RFC2047 in headers.
>
>
You'll have to ask someone else for that. I have no idea how it works
and I wouldn't know how to begin doing it in shell.
--
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-09 2:01 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
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 [this message]
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=43C1C3FA.8070609@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.