"H. Peter Anvin" [off-list ref] writes:
Junio C Hamano wrote:
quoted
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.
Fair enough. "--encoding=<encoding>" then.
Incidentally, any reason we're not using getopt_long() for command-line
parsing?
There was a talk about using popt a while back but we never got
around to it, primarily because we were running too fast for
parties interested in command line parsing clean-ups to catch
up. I think we are almost done and immediately post 1.0 when
things stabilize may be a good time to do it if somebody wants
to go wild, but not before please.