Improve error messages when int/long cannot be parsed from config
If a config file has become mildly corrupted due to a missing LF we may discover some other option joined up against the end of a numeric value. For example:
[section] number = 1auto
where the "auto" flag was meant to occur on the next line, below "number", but the missing LF has caused it to no longer be its own option. Instead the word "auto" is parsed as a 'unit factor' for the value of "number".
Before this change we got the confusing error message:
fatal: unknown unit: 'auto'
which told us nothing about where the problem appeared. Now we get:
fatal: bad config value for 'aninvalid.unit'
which at least points the user in the right direction of where to search for the incorrectly formatted configuration file.
Noticed by erikh on #git, which received the original error from a simple `git checkout -b` due to a midly corrupted config.
Signed-off-by: Shawn O. Pearce <email@example.com> Signed-off-by: Junio C Hamano <firstname.lastname@example.org>