git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russ Allbery <rra@debian.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Stefan-W. Hahn" <stefan.hahn@s-hahn.de>,
	"Lukas Sandström" <luksan@gmail.com>, "Jeff King" <peff@peff.net>,
	"Christian Himpel" <chressie@googlemail.com>
Subject: Re: git am should recognize >From
Date: Sun, 19 Sep 2010 11:01:47 -0700	[thread overview]
Message-ID: <87wrqheho4.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <AANLkTinOa+s-28PYXHhtKr_POu2D33ibfgKDKk4Wqi=9@mail.gmail.com> (Jonathan Nieder's message of "Sun, 19 Sep 2010 17:32:11 +0300")

Jonathan Nieder <jrnieder@gmail.com> writes:

> Aside: it seems that many format-patch users are not using it to
> generate an mbox with a template message, as originally intended;

Myself included.  I don't like other things sending mail for me outside of
my normal mail client, since my normal mail client does lots of other
things (like know what From address to use, save copies of outgoing mail,
etc.).

> instead, they just write a cover letter and attach the generated patches
> to it. Are we not advertising the "am --scissors" facility[1] well
> enough?

That seems like a bad substitute for real MIME structure.  My experience
is that patches as actual MIME attachments fare much better and are much
less likely to be mangled when getting to the committer than patches
inlined in the body of a message.  (Yes, this is a 180 degree reversal
from the situation about ten years ago.)

Speaking of git am features, it would also be lovely if git am would
recognize and accept the format produced by git show, since a lot of
beginning Git users tend towards git show output instead of git
format-patch.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

  reply	other threads:[~2010-09-19 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19 14:24 git am should recognize >From Jonathan Nieder
2010-09-19 14:32 ` Jonathan Nieder
2010-09-19 18:01   ` Russ Allbery [this message]
2010-09-19 18:38   ` Make format-patch produce UTF-8 `From:' header (was Re: git am should recognize >From) Štěpán Němec
2010-09-19 19:19     ` Make format-patch produce UTF-8 `From:' header Russ Allbery
2010-09-20 12:20       ` use base64 instead of quoted-printable in format-patch headers (was Re: Make format-patch produce UTF-8 `From:' header) Štěpán Němec
2010-09-20 13:46         ` Ævar Arnfjörð Bjarmason
2010-09-20 15:29           ` Brandon Casey
2010-09-20 15:55           ` use base64 instead of quoted-printable in format-patch headers Štěpán Němec
2010-09-19 19:44     ` Make format-patch produce UTF-8 `From:' header (was Re: git am should recognize >From) Erik Faye-Lund

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=87wrqheho4.fsf@windlord.stanford.edu \
    --to=rra@debian.org \
    --cc=chressie@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=luksan@gmail.com \
    --cc=peff@peff.net \
    --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;
as well as URLs for NNTP newsgroup(s).