{"thread":{"id":"38496","subject":"Invalid responses to 8bit encoding and In-Reply-To questions","startedAt":"2015-02-04T09:07:15Z","lastAt":"2015-04-01T18:03:38Z","messageCount":4,"participants":["Geert Uytterhoeven","Junio C Hamano","Guilhem Bichot"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"255602","messageId":"CAMuHMdWbHMPEwkYvzKzzc6L0T8ufk62DGS2sZ1w1BthL1kAZWA@mail.gmail.com","threadId":"38496","inReplyTo":null,"subject":"Invalid responses to 8bit encoding and In-Reply-To questions","fromName":"Geert Uytterhoeven","fromEmail":"geert@linux-m68k.org","sentAt":"2015-02-04T09:07:15Z","receivedAt":"2015-02-04T09:07:15Z","isPatch":false,"sender":{"key":"geert@linux-m68k.org","avatar":"https://gravatar.com/avatar/8105b34f653a7b5b98e225e565b11ebcc762ad4ab1a9d905a4663db029a9e6bc?d=mp&s=160"},"body":">From a thread on another mailing list:\n| > Content-Type: text/plain; charset=y\n| > Content-Transfer-Encoding: 8bit\n| >\n| > When I try to apply it git am says:\n| >\n| > $ git am --signoff geert1.patch\n| > fatal: cannot convert from y to UTF-8\n| >\n| > Wut? I never heard of an encoding named \"y\", and SMTP is\n| > not my strongest subject anyway.\n|\n| Oops, I'm afraid automatic-I replied \"y\" to the git-send-email question\n| \"Which 8bit encoding should I declare [UTF-8]?\"\n| (happened before with the In-Reply-To questions ;-(\n\nWould it be possible to reject obviously wrong replies (\"y\", \"yes\", \"n\", \"no\")\nto the 8bit encoding and In-Reply-To questions?\n\nThanks!\n\nGr{oetje,eeting}s,\n\n Geert\n\n--\nGeert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org\n\nIn personal conversations with technical people, I call myself a hacker. But\nwhen I'm talking to journalists I just say \"programmer\" or something like that.\n -- Linus Torvalds\n"},{"id":"255607","messageId":"xmqqa90to78v.fsf@gitster.dls.corp.google.com","threadId":"38496","inReplyTo":"CAMuHMdWbHMPEwkYvzKzzc6L0T8ufk62DGS2sZ1w1BthL1kAZWA@mail.gmail.com","subject":"Re: Invalid responses to 8bit encoding and In-Reply-To questions","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2015-02-04T18:34:56Z","receivedAt":"2015-02-04T18:34:56Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Geert Uytterhoeven writes:\n\n> | Oops, I'm afraid automatic-I replied \"y\" to the git-send-email question\n> | \"Which 8bit encoding should I declare [UTF-8]?\"\n> | (happened before with the In-Reply-To questions ;-(\n>\n> Would it be possible to reject obviously wrong replies (\"y\", \"yes\", \"n\", \"no\")\n> to the 8bit encoding and In-Reply-To questions?\n\nThere is no canned configuration to do so, if that is what you are\nasking.\n\nIt would be possible to do so with code changes to git-send-email;\nlook for \"ask(\", \"valid_re\", and \"confirm_only\" to see how they are\nused in existing code that ask questions, if you are interested.\n"},{"id":"258818","messageId":"loom.20150401T125113-830@post.gmane.org","threadId":"38496","inReplyTo":"xmqqa90to78v.fsf@gitster.dls.corp.google.com","subject":"Re: Invalid responses to 8bit encoding and In-Reply-To questions","fromName":"Guilhem Bichot","fromEmail":"guilhem.bichot@oracle.com","sentAt":"2015-04-01T10:53:11Z","receivedAt":"2015-04-01T10:53:11Z","isPatch":false,"sender":{"key":"guilhem.bichot@oracle.com","avatar":null},"body":"Junio C Hamano pobox.com> writes:\n\n> \n> Geert Uytterhoeven linux-m68k.org> writes:\n> \n> > | Oops, I'm afraid automatic-I replied \"y\" to the git-send-email question\n> > | \"Which 8bit encoding should I declare [UTF-8]?\"\n> > | (happened before with the In-Reply-To questions ;-(\n> >\n> > Would it be possible to reject obviously wrong replies (\"y\", \"yes\", \"n\",\n\"no\")\n> > to the 8bit encoding and In-Reply-To questions?\n> \n> There is no canned configuration to do so, if that is what you are\n> asking.\n> \n> It would be possible to do so with code changes to git-send-email;\n> look for \"ask(\", \"valid_re\", and \"confirm_only\" to see how they are\n> used in existing code that ask questions, if you are interested.\n\nToday I stumbled on exactly this; a colleague had probably typed \"yes\" when\ninappropriate, and the email I received from git-send-email had:\n\nContent-Type: text/plain; charset=yes\n\nthen \"git am\" complained.\n"},{"id":"258834","messageId":"xmqq8uebn2th.fsf@gitster.dls.corp.google.com","threadId":"38496","inReplyTo":"loom.20150401T125113-830@post.gmane.org","subject":"Re: Invalid responses to 8bit encoding and In-Reply-To questions","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2015-04-01T18:03:38Z","receivedAt":"2015-04-01T18:03:38Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Guilhem Bichot writes:\n\n> Junio C Hamano pobox.com> writes:\n>\n>> It would be possible to do so with code changes to git-send-email;\n>> look for \"ask(\", \"valid_re\", and \"confirm_only\" to see how they are\n>> used in existing code that ask questions, if you are interested.\n>\n> Today I stumbled on exactly this; a colleague had probably typed \"yes\" when\n> inappropriate, and the email I received from git-send-email had:\n>\n> Content-Type: text/plain; charset=yes\n\nThen upcoming release Git 2.4.0 will delight you ;-)\n"}]}