gmail screws up patches looking for workable workaround

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux