Propogate GIT_ENOTFOUND from git_remote_rename

Make config reading continue after hitting a missing include file.

Changed context_lines and interhunk_lines to uint32_t to match struct s_xdemitconf

remote: unify the creation code

netops: return GIT_ECERTIFICATE when it fails the basic tests

Fix segmentation fault observed on OpenBSD/sparc64

Make the Visual Studio compiler happy

A non-readable mapping of a file causes an access violation in
the pack tests. Always use PROT_READ to work around this.

* Error-handling is cleaned up to only let a file-not-found error
  through, not other sorts of errors.  And when a file-not-found
  error happens, we clean up the error.
* Test now checks that file-not-found introduces no error.  And
  other minor cleanups.

The create function with default refspec is the same as the one with a
custom refspec, but it has the default refspec, so we can create the one
on top of the other.

An anonymous remote wouldn't create remote-tracking branches, so testing
we don't create them for TAGS_ALL is nonsensical. Furthermore, the name
of the supposed remote-tracking branch was also not one which would have
been created had it had a name.

Give the remote a name and test that we only create the tags when we
pass TAGS_ALL and that we do create the remote-branch branch when given
TAGS_AUTO.

Since it's not necessarily obvious, mention the merging state and how to
clear it.

When we first ask OpenSSL to verify the certfiicate itself (rather
than the HTTPS specifics), we should also return
GIT_ECERTIFICATE. Otherwise, the caller would consider this as a failed
operation rather than a failed validation and not call the user's own
validation.

For example, if you have

[include]
path = foo

and foo didn't exist, git_config_open_ondisk() would just give up
on the rest of the file.  Now it ignores the unresolved include
without error and continues reading the rest of the file.

revert tests: always use core.autocrlf=false in tests

Fixed the most obvious Clang static analyzer warnings

Flip THREADSAFE's default to ON

Threads are here to stay; and for a while now, users have had to call
the initialization function which sets up threads and crypto regardless
of whether the library was built threadsafe or not.

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

Rebase (merge)

Rename git_merge_head to git_annotated_commit, as it becomes used
in more operations than just merge.