Re: gmail screws up patches looking for workable workaround
- From
Caleb Cushing <xenoterracide@gmail.com>
- Date
- Feb 13, 2009, 18:00 UTC
- Message-ID
- <81bfc67a0902131000n2d67e88epd743c7c39842fbc@mail.gmail.com>
- In-Reply-To
- <8c9a060902130926j48b59785l624a3966254517e5@mail.gmail.com>
Show 15 quoted lines
> ~/.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 = tlseverything 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