We always calculate multiple merge bases, but up to now we had only
exposed the "best" merge base.

Introduce git_oidarray which analogously to git_strarray lets us return
multiple ids.

Export git_buf_text_is_binary and git_buf_text_contains_nul.

When adding new config section, handle config file not ending with LF

Handle local file:/// paths on Windows

So that users don’t need to implement binary detection themselves.

Update perl bindings link

Switch description and message reporting in `clar__assert_equal_file`

Windows can't handle a path like `/c:/foo`; when turning file:///
URIs into local paths, we must strip the leading slash.

Windows compatibility fixes 

ssh: provide a factory function for setting ssh paths

Support refspecs with the asterisk in the middle

Properly report failure when expanding a packfile

merge: don't open COMMIT_MSG unless we need to append conflicts

Fixup git_attr_value's comment to be recognised as documentation, and
include the definitions needed for clang to parse reset.h such that
it shows up in the documentation.

This fixes #2430.

git allows you to set which paths to use for the git server programs
when connecting over ssh; and we want to provide something similar.

We do this by providing a factory function which can be set as the
remote's transport callback which will set the given paths upon
creation.

We used to assume a refspec would only have an asterisk in the middle of
their respective pattern. This has not been a valid assumption for some
time now with git.

Instead of assuming where the asterisk is going to be, change the logic
to treat each pattern as having two halves with a replacement bit in the
middle, where the asterisk is.

When transforming a non-pattern refspec, we simply need to copy over the
opposite string. Move that logic up to the wrapper so we can assume a
pattern refspec in the transformation function.

Fix SSH2 warnings

Move yield to the tests and enable for FreeBSD