git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Cushing <xenoterracide@gmail.com>
To: git@vger.kernel.org
Cc: Dan Robbins <drobbins@funtoo.org>
Subject: gmail screws up patches looking for workable workaround
Date: Fri, 13 Feb 2009 12:09:47 -0500	[thread overview]
Message-ID: <81bfc67a0902130909i154a7c2epeff98347985c3fb8@mail.gmail.com> (raw)

I've followed all the steps in the git Submitting patches guide. In
fact it works fine for any patch where all lines are less than 80?
chars. however, some of the patches store sha256 hashes (and the like)
and have really long lines and gmail word wraps them.

I've tried submitting patches as follows.

git format-patch -1 -M --stdout | git imap-send

git format-patch -1 -M --stdout --attach | git imap-send

git format-patch -1 -M --stdout --inline | git imap-send


we know the first corrupts the patches. but what I can't figure out is
why the next 2 don't work on the receiving end. The comment was.


git am -3 -i, when I choose [v]iew patch, I get a binary output.


I'm trying to figure out how I can submit patches via gmail for
someone that uses git am. what is being done wrong?

-- 
Caleb Cushing

http://xenoterracide.blogspot.com

             reply	other threads:[~2009-02-13 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 17:09 Caleb Cushing [this message]
2009-02-13 17:26 ` gmail screws up patches looking for workable workaround Jacob Helwig
2009-02-13 18:00   ` Caleb Cushing
2009-02-13 18:11     ` Jacob Helwig
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=81bfc67a0902130909i154a7c2epeff98347985c3fb8@mail.gmail.com \
    --to=xenoterracide@gmail.com \
    --cc=drobbins@funtoo.org \
    --cc=git@vger.kernel.org \
    /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).