{"thread":{"id":"17775","subject":"gmail screws up patches looking for workable workaround","startedAt":"2009-02-13T17:09:47Z","lastAt":"2009-02-14T00:46:41Z","messageCount":7,"participants":["Caleb Cushing","Jacob Helwig","Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"104528","messageId":"81bfc67a0902130909i154a7c2epeff98347985c3fb8@mail.gmail.com","threadId":"17775","inReplyTo":null,"subject":"gmail screws up patches looking for workable workaround","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-02-13T17:09:47Z","receivedAt":"2009-02-13T17:09:47Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"I've followed all the steps in the git Submitting patches guide. In\nfact it works fine for any patch where all lines are less than 80?\nchars. however, some of the patches store sha256 hashes (and the like)\nand have really long lines and gmail word wraps them.\n\nI've tried submitting patches as follows.\n\ngit format-patch -1 -M --stdout | git imap-send\n\ngit format-patch -1 -M --stdout --attach | git imap-send\n\ngit format-patch -1 -M --stdout --inline | git imap-send\n\n\nwe know the first corrupts the patches. but what I can't figure out is\nwhy the next 2 don't work on the receiving end. The comment was.\n\n\ngit am -3 -i, when I choose [v]iew patch, I get a binary output.\n\n\nI'm trying to figure out how I can submit patches via gmail for\nsomeone that uses git am. what is being done wrong?\n\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"104530","messageId":"8c9a060902130926j48b59785l624a3966254517e5@mail.gmail.com","threadId":"17775","inReplyTo":"81bfc67a0902130909i154a7c2epeff98347985c3fb8@mail.gmail.com","subject":"Re: gmail screws up patches looking for workable workaround","fromName":"Jacob Helwig","fromEmail":"jacob.helwig@gmail.com","sentAt":"2009-02-13T17:26:21Z","receivedAt":"2009-02-13T17:26:21Z","isPatch":false,"sender":{"key":"jacob.helwig@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14557?v=4"},"body":"On Fri, Feb 13, 2009 at 09:09, Caleb Cushing wrote:\n> I've followed all the steps in the git Submitting patches guide. In\n> fact it works fine for any patch where all lines are less than 80?\n> chars. however, some of the patches store sha256 hashes (and the like)\n> and have really long lines and gmail word wraps them.\n>\n> I've tried submitting patches as follows.\n>\n> git format-patch -1 -M --stdout | git imap-send\n>\n> git format-patch -1 -M --stdout --attach | git imap-send\n>\n> git format-patch -1 -M --stdout --inline | git imap-send\n>\n>\n> we know the first corrupts the patches. but what I can't figure out is\n> why the next 2 don't work on the receiving end. The comment was.\n>\n>\n> git am -3 -i, when I choose [v]iew patch, I get a binary output.\n>\n>\n> I'm trying to figure out how I can submit patches via gmail for\n> someone that uses git am. what is being done wrong?\n>\n> --\n> Caleb Cushing\n>\n> http://xenoterracide.blogspot.com\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n>\n\nThis is the setup I use for emailing patches using git:\n\n~/.gitconfig\n[sendemail]\n smtpserver = smtp.gmail.com\n smtpserverport = 587\n smtpuser = your.email@gmail.com\n smtppass = yourPassword\n smtpencryption = tls\n\n$ git format-patch \n# add comments to 00*.patch files.\n$ git send-email 00*\n\nI've never seen any mangling using send-email, and the gmail SMTP\nserver. I've never actually tried using imap-send. Not quite the\nanswer to your question, but hopefully, it's another option.\n"},{"id":"104535","messageId":"81bfc67a0902131000n2d67e88epd743c7c39842fbc@mail.gmail.com","threadId":"17775","inReplyTo":"8c9a060902130926j48b59785l624a3966254517e5@mail.gmail.com","subject":"Re: gmail screws up patches looking for workable workaround","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-02-13T18:00:32Z","receivedAt":"2009-02-13T18:00:32Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"> ~/.gitconfig\n> [sendemail]\n> smtpserver = smtp.gmail.com\n> smtpserverport = 587\n> smtpuser = your.email@gmail.com\n> smtppass = yourPassword\n> smtpencryption = tls\n>\n> $ git format-patch \n> # add comments to 00*.patch files.\n> $ git send-email 00*\n> I've never seen any mangling using send-email, and the gmail SMTP\n> server. I've never actually tried using imap-send. Not quite the\n> answer to your question, but hopefully, it's another option.\n>\n\n[sendmail]\n smtpserver = smtp.gmail.com\n smtpserverport = 587\n smtpuser = xenoterracide@gmail.com\n smtppass = YeahITypedThisRight\n smtpencryption = tls\n\neverything look good here? because mail isn't actually reaching it's\ndestination. I have a feeling that's because the MTA isn't set up. I\n/could/ set that up... but I don't think that's something that anyone\nshould have to do to send email patches.\n\nalso according to someone else the reason git can't handle the\nattachments is because they are still base64 encoded.\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"104537","messageId":"8c9a060902131011u5bc7d0dft4edc4adb1af1dad8@mail.gmail.com","threadId":"17775","inReplyTo":"81bfc67a0902131000n2d67e88epd743c7c39842fbc@mail.gmail.com","subject":"Re: gmail screws up patches looking for workable workaround","fromName":"Jacob Helwig","fromEmail":"jacob.helwig@gmail.com","sentAt":"2009-02-13T18:11:19Z","receivedAt":"2009-02-13T18:11:19Z","isPatch":false,"sender":{"key":"jacob.helwig@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14557?v=4"},"body":"On Fri, Feb 13, 2009 at 10:00, Caleb Cushing wrote:\n>> ~/.gitconfig\n>> [sendemail]\n>> smtpserver = smtp.gmail.com\n>> smtpserverport = 587\n>> smtpuser = your.email@gmail.com\n>> smtppass = yourPassword\n>> smtpencryption = tls\n>>\n>> $ git format-patch \n>> # add comments to 00*.patch files.\n>> $ git send-email 00*\n>> I've never seen any mangling using send-email, and the gmail SMTP\n>> server. I've never actually tried using imap-send. Not quite the\n>> answer to your question, but hopefully, it's another option.\n>>\n>\n> [sendmail]\n> smtpserver = smtp.gmail.com\n> smtpserverport = 587\n> smtpuser = xenoterracide@gmail.com\n> smtppass = YeahITypedThisRight\n> smtpencryption = tls\n>\n> everything look good here? because mail isn't actually reaching it's\n> destination. I have a feeling that's because the MTA isn't set up. I\n> /could/ set that up... but I don't think that's something that anyone\n> should have to do to send email patches.\n>\n> also according to someone else the reason git can't handle the\n> attachments is because they are still base64 encoded.\n> --\n> Caleb Cushing\n>\n> http://xenoterracide.blogspot.com\n>\n\n\"git imap-send\" doesn't use the [sendmail] section of the .gitconfig.\nIt uses the [imap] section. The [sendmail] configuration is if you're\nusing \"git send-email\".\n\nIf you setup the smtp* options, you don't need a local MTA, since\nsend-email will use the SMTP server you configured.\n\nAre you still getting the corruption if you let format-patch generate\nthe patch on disk (don't use the --stdout option), and give the patch\nfilename(s) as the final arguments to send-email? (Could you show the\nnew sequence of commands you're using, and what the output is?)\n"},{"id":"104538","messageId":"81bfc67a0902131020w66e114b7ke642ab8308e530c3@mail.gmail.com","threadId":"17775","inReplyTo":"8c9a060902131011u5bc7d0dft4edc4adb1af1dad8@mail.gmail.com","subject":"Re: gmail screws up patches looking for workable workaround","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-02-13T18:20:46Z","receivedAt":"2009-02-13T18:20:46Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"> \"git imap-send\" doesn't use the [sendmail] section of the .gitconfig.\n> It uses the [imap] section. The [sendmail] configuration is if you're\n> using \"git send-email\".\n\nyeah... I've both set up, and followed your sendmail instructions explicitly\n\n> If you setup the smtp* options, you don't need a local MTA, since\n> send-email will use the SMTP server you configured.\n\ntell that to the postdrop (postfix) error that I saw on the screen.\n\n> Are you still getting the corruption if you let format-patch generate\n> the patch on disk (don't use the --stdout option), and give the patch\n> filename(s) as the final arguments to send-email? (Could you show the\n> new sequence of commands you're using, and what the output is?)\n>\n\nno... no corruption locally. the problem is the mail never arrives. I\ndon't know where it disappears at, but it doesn't make it to the inbox\nI send it to, and I really, really, really do not want to troubleshoot\nany of the 1000 places it could have gone wrong\n\n git send-email 00*\n0001-remove-mysql-community-5.1-beta.patch\nWho should the emails appear to be from? [Caleb Cushing\n]\nEmails will be sent from: Caleb Cushing \nWho should the emails be sent to? xenoterracide@gmail.com\nMessage-ID to be used as In-Reply-To for the first email?\nxenoterracide@gmail.com\n(mbox) Adding cc: Caleb Cushing from line\n'From: Caleb Cushing '\n(sob) Adding cc: Caleb Cushing from line\n'Signed-off-by: Caleb Cushing '\npostdrop: warning: unable to look up public/pickup: No such file or directory\nOK. Log says:\nSendmail: /usr/sbin/sendmail -i xenoterracide@gmail.com\nFrom: Caleb Cushing \nTo: xenoterracide@gmail.com\nSubject: [PATCH] remove mysql-community-5.1*beta\nDate: Fri, 13 Feb 2009 13:19:14 -0500\nMessage-Id: <1234549154-24500-1-git-send-email-xenoterracide@gmail.com>\nX-Mailer: git-send-email 1.6.1.3\nIn-Reply-To: \nReferences: \n\nResult: OK\n\nand yet no email ever arrives at my inbox. (or spam for that matter)\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"104542","messageId":"8c9a060902131135m2b8e89d3s25d3b4455dae0f32@mail.gmail.com","threadId":"17775","inReplyTo":"81bfc67a0902131020w66e114b7ke642ab8308e530c3@mail.gmail.com","subject":"Re: gmail screws up patches looking for workable workaround","fromName":"Jacob Helwig","fromEmail":"jacob.helwig@gmail.com","sentAt":"2009-02-13T19:35:47Z","receivedAt":"2009-02-13T19:35:47Z","isPatch":false,"sender":{"key":"jacob.helwig@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14557?v=4"},"body":"On Fri, Feb 13, 2009 at 10:20, Caleb Cushing wrote:\n>> \"git imap-send\" doesn't use the [sendmail] section of the .gitconfig.\n>> It uses the [imap] section. The [sendmail] configuration is if you're\n>> using \"git send-email\".\n>\n> yeah... I've both set up, and followed your sendmail instructions explicitly\n>\n>> If you setup the smtp* options, you don't need a local MTA, since\n>> send-email will use the SMTP server you configured.\n>\n> tell that to the postdrop (postfix) error that I saw on the screen.\n>\n>> Are you still getting the corruption if you let format-patch generate\n>> the patch on disk (don't use the --stdout option), and give the patch\n>> filename(s) as the final arguments to send-email? (Could you show the\n>> new sequence of commands you're using, and what the output is?)\n>>\n>\n> no... no corruption locally. the problem is the mail never arrives. I\n> don't know where it disappears at, but it doesn't make it to the inbox\n> I send it to, and I really, really, really do not want to troubleshoot\n> any of the 1000 places it could have gone wrong\n>\n> git send-email 00*\n> 0001-remove-mysql-community-5.1-beta.patch\n> Who should the emails appear to be from? [Caleb Cushing\n> ]\n> Emails will be sent from: Caleb Cushing \n> Who should the emails be sent to? xenoterracide@gmail.com\n> Message-ID to be used as In-Reply-To for the first email?\n> xenoterracide@gmail.com\n> (mbox) Adding cc: Caleb Cushing from line\n> 'From: Caleb Cushing '\n> (sob) Adding cc: Caleb Cushing from line\n> 'Signed-off-by: Caleb Cushing '\n> postdrop: warning: unable to look up public/pickup: No such file or directory\n> OK. Log says:\n> Sendmail: /usr/sbin/sendmail -i xenoterracide@gmail.com\n\nI should have looked more closely, when you posted your config. You\nhave \"[sendmail]\", instead of \"[sendemail]\". You're missing the \"e\"\non \"email\". What made me re-look is the line right after \"OK. Log\nsays:\".\n\nYou should have seen:\nOK. Log says:\nServer: smtp.gmail.com\n\nNot:\nOK. Log says:\nSendmail: /usr/sbin/sendmail -i xenoterracide@gmail.com\n"},{"id":"104562","messageId":"slrngpc53h.jdo.sitaramc@sitaramc.homelinux.net","threadId":"17775","inReplyTo":"81bfc67a0902131000n2d67e88epd743c7c39842fbc@mail.gmail.com","subject":"Re: gmail screws up patches looking for workable workaround","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-02-14T00:46:41Z","receivedAt":"2009-02-14T00:46:41Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On 2009-02-13, Caleb Cushing wrote:\n>> ~/.gitconfig\n>> [sendemail]\n\n> [sendmail]\n\n> everything look good here? because mail isn't actually reaching it's\n\nno :-) you're missing an 'e'. Not sure if that makes a\ndifference\n"}]}