The `parse_variable` function has two out parameters `var_name` and
`var_value`. Currently, those are not being sanitized to `NULL`. when.
any error happens inside of the `parse_variable` function. Fix that.
While at it, the coding style is improved to match our usual coding
practices more closely.

The function `git_config_parse` uses several callbacks to pass data
along to the caller as it parses the file. One design shortcoming here
is that strings passed to those callbacks are expected to be freed by
them, which is really confusing.

Fix the issue by changing memory ownership here. Instead of expecting
the `on_variable` callbacks to free memory for `git_config_parse`, just
do it inside of `git_config_parse`. While this obviously requires a bit
more memory allocation churn due to having to copy both name and value
at some places, this shouldn't be too much of a burden.

Fix last references to deprecated git_buf_free

revwalk: avoid walking the entire history when output is unsorted

Signed-off-by: Sven Strickroth <email@cs-ware.de>

Add mailmap support.

tree: remove unused functions

Link `mbedTLS` libraries in when `SHA1_BACKEND` == "mbedTLS"

editorconfig: allow trailing whitespace in markdown

Also matches git.

This matches git.

Not that it matters much anyway but...

docs: fix statement about tab width

diff: fix enum value being out of allowed range

The libgit2 project mostly follows the coding style of git and thus
the linux project. While those two projects use a recommended tab width
of eight spaces, we instruct users to set their editor's tab width to
four spaces. Fix this to say eight instead.