Invalid responses to 8bit encoding and In-Reply-To questions

| > Content-Type: text/plain; charset=y
| > Content-Transfer-Encoding: 8bit
| >
| > When I try to apply it git am says:
| >
| > $ git am --signoff geert1.patch
| > fatal: cannot convert from y to UTF-8
| >
| > Wut? I never heard of an encoding named "y", and SMTP is
| > not my strongest subject anyway.
|
| Oops, I'm afraid automatic-I replied "y" to the git-send-email question
| "Which 8bit encoding should I declare [UTF-8]?"
| (happened before with the In-Reply-To questions ;-(

Would it be possible to reject obviously wrong replies ("y", "yes", "n", "no") to the 8bit encoding and In-Reply-To questions?

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Geert Uytterhoeven <geert@linux-m68k.org> writes:

There is no canned configuration to do so, if that is what you are asking.

It would be possible to do so with code changes to git-send-email; look for "ask(", "valid_re", and "confirm_only" to see how they are used in existing code that ask questions, if you are interested.

Junio C Hamano <gitster <at> pobox.com> writes:

"no")

Today I stumbled on exactly this; a colleague had probably typed "yes" when inappropriate, and the email I received from git-send-email had:

Content-Type: text/plain; charset=yes

then "git am" complained.

Guilhem Bichot <guilhem.bichot@oracle.com> writes:

Then upcoming release Git 2.4.0 will delight you ;-)