git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Cushing <xenoterracide@gmail.com>
To: Jacob Helwig <jacob.helwig@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 13:20:46 -0500	[thread overview]
Message-ID: <81bfc67a0902131020w66e114b7ke642ab8308e530c3@mail.gmail.com> (raw)
In-Reply-To: <8c9a060902131011u5bc7d0dft4edc4adb1af1dad8@mail.gmail.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".

yeah... I've both set up, and followed your sendmail instructions explicitly

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

tell that to the postdrop (postfix) error that I saw on the screen.

> 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?)
>

no... no corruption locally. the problem is the mail never arrives. I
don't know where it disappears at, but it doesn't make it to the inbox
I send it to, and I really, really, really do not want to troubleshoot
any of the 1000 places it could have gone wrong

 git send-email 00*
0001-remove-mysql-community-5.1-beta.patch
Who should the emails appear to be from? [Caleb Cushing
<xenoterracide@gmail.com>]
Emails will be sent from: Caleb Cushing <xenoterracide@gmail.com>
Who should the emails be sent to? xenoterracide@gmail.com
Message-ID to be used as In-Reply-To for the first email?
xenoterracide@gmail.com
(mbox) Adding cc: Caleb Cushing <xenoterracide@gmail.com> from line
'From: Caleb Cushing <xenoterracide@gmail.com>'
(sob) Adding cc: Caleb Cushing <xenoterracide@gmail.com> from line
'Signed-off-by: Caleb Cushing <xenoterracide@gmail.com>'
postdrop: warning: unable to look up public/pickup: No such file or directory
OK. Log says:
Sendmail: /usr/sbin/sendmail -i xenoterracide@gmail.com
From: Caleb Cushing <xenoterracide@gmail.com>
To: xenoterracide@gmail.com
Subject: [PATCH] remove mysql-community-5.1*beta
Date: Fri, 13 Feb 2009 13:19:14 -0500
Message-Id: <1234549154-24500-1-git-send-email-xenoterracide@gmail.com>
X-Mailer: git-send-email 1.6.1.3
In-Reply-To: <xenoterracide@gmail.com>
References: <xenoterracide@gmail.com>

Result: OK

and yet no email ever arrives at my inbox. (or spam for that matter)
-- 
Caleb Cushing

http://xenoterracide.blogspot.com

  reply	other threads:[~2009-02-13 18:22 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
2009-02-13 18:20       ` Caleb Cushing [this message]
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=81bfc67a0902131020w66e114b7ke642ab8308e530c3@mail.gmail.com \
    --to=xenoterracide@gmail.com \
    --cc=drobbins@funtoo.org \
    --cc=git@vger.kernel.org \
    --cc=jacob.helwig@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).