Re: gmail screws up patches looking for workable workaround

On Fri, Feb 13, 2009 at 10:00, Caleb Cushing [off-list ref] wrote:

quoted

~/.gitconfig
[sendemail]
   smtpserver = smtp.gmail.com
   smtpserverport = 587
   smtpuser = your.email@gmail.com
   smtppass = yourPassword
   smtpencryption = tls

$ git format-patch <options>
# add comments to 00*.patch files.
$ git send-email 00*
I've never seen any mangling using send-email, and the gmail SMTP
server.  I've never actually tried using imap-send.  Not quite the
answer to your question, but hopefully, it's another option.

[sendmail]
   smtpserver = smtp.gmail.com
   smtpserverport = 587
   smtpuser = xenoterracide@gmail.com
   smtppass = YeahITypedThisRight
   smtpencryption = tls

everything look good here? because mail isn't actually reaching it's
destination. I have a feeling that's because the MTA isn't set up. I
/could/ set that up... but I don't think that's something that anyone
should have to do to send email patches.

also according to someone else the reason git can't handle the
attachments is because they are still base64 encoded.
--
Caleb Cushing

http://xenoterracide.blogspot.com

"git imap-send" doesn't use the [sendmail] section of the .gitconfig.
It uses the [imap] section.  The [sendmail] configuration is if you're
using "git send-email".

If you setup the smtp* options, you don't need a local MTA, since
send-email will use the SMTP server you configured.

Are you still getting the corruption if you let format-patch generate
the patch on disk (don't use the --stdout option), and give the patch
filename(s) as the final arguments to send-email?  (Could you show the
new sequence of commands you're using, and what the output is?)