Junio C Hamano wrote:
When the message body does not identify what encoding it is in,
-u assumes it is in latin-1 and converts it to utf8, which is
the recommended encoding for git commit log messages.
With -u=<encoding>, the conversion is made into the specified
one, instead of utf8, to allow project-local policies.
Signed-off-by: Junio C Hamano <redacted>
-u= is very odd syntax. Typically you see "-u argument" (sometimes you
have "-u" and "-U argument" as a pair); --foo=argument is used for long
options, although even there "--foo argument" tends to be used at least
when the argument is required.
Incidentally, any reason we're not using getopt_long() for command-line
parsing?
-hpa