Re: Using `git send-email` (was: Number 1 tip for getting your patch committed)

[Mark Brown <broonie@sirena.org.uk>]

On Sat, Jan 23, 2010 at 11:06:22PM +0100, Paul Menzel wrote:

> Secondly for a lot of people using `git send-email` is no option because
> setup is too difficult, their MUA does not integrate well with `git
> send-email` so the address book is not available, they do want to have
> sent messages archived in their Sent folder, they want to ask some
> questions regarding the patch and therefore need to write a message and
> attach it.

There's also other variants like git imap-send.  The send-email
suggestion could be rewritten as "do something which git am understands
out of the box", it's approximately equivalent.

> In my opinion we should therefore find a way to also work easily with
> attached patches having been created with `git format-patch`. Can some
> of the developers mention what the disadvantage of attached patches is.
> You can easily quote them to and saving and applying should be as easy
> as with messages sent using `git send-email`.

> The only disadvantage I can think of seems to be that it is not
> displayed in the mailing list archive.

Attaching patches also upsets most tools, they tend to assume that the
body of the mail is supposed to be part of the commit message (which it
would normally be) which tends not to look too pretty.  Replying can be
an issue with some MUAs too, especially if the attachment gets reencoded
due to not being seven bit clean.