From: Jacob Helwig <jacob.helwig@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: git@vger.kernel.org, Dan Robbins <drobbins@funtoo.org>
Subject: Re: gmail screws up patches looking for workable workaround
Date: Fri, 13 Feb 2009 10:11:19 -0800 [thread overview]
Message-ID: <8c9a060902131011u5bc7d0dft4edc4adb1af1dad8@mail.gmail.com> (raw)
In-Reply-To: <81bfc67a0902131000n2d67e88epd743c7c39842fbc@mail.gmail.com>
On Fri, Feb 13, 2009 at 10:00, Caleb Cushing <xenoterracide@gmail.com> wrote:
>> ~/.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?)
next prev parent reply other threads:[~2009-02-13 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 17:09 gmail screws up patches looking for workable workaround Caleb Cushing
2009-02-13 17:26 ` Jacob Helwig
2009-02-13 18:00 ` Caleb Cushing
2009-02-13 18:11 ` Jacob Helwig [this message]
2009-02-13 18:20 ` Caleb Cushing
2009-02-13 19:35 ` Jacob Helwig
2009-02-14 0:46 ` Sitaram Chamarty
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=8c9a060902131011u5bc7d0dft4edc4adb1af1dad8@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=drobbins@funtoo.org \
--cc=git@vger.kernel.org \
--cc=xenoterracide@gmail.com \
/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).