If we find several objects with the same prefix, we need to free the
memory where we stored the earlier object. Keep track of the raw.data
pointer across read_prefix calls and free it if we find another
object.

Make index add/append support core.filemode flag

message: Expose git_message_prettify()

oid_for_tree_path may not always find the path in the tree, in which
case we need to return an error. The current code doesn't do this and
results in undefined behavior.

This fixes git_index_add and git_index_append to behave more like
core git, preserving old filemode data in the index when adding
and/or appending with core.filemode = false.

This also has placeholder support for core.symlinks and
core.ignorecase, but those flags are not implemented (well,
symlinks has partial support for preserving mode information in
the same way that git does, but it isn't tested).

Fix potential segfault in revparse.

git_commit() and git_tag() no longer prettify the
message by default. This has to be taken care of
by the caller.

This has the nice side effect of putting the
caller in position to actually choose to strip
the comments or not.

Quotes inside config values don't survive serialization/deserialization

Expose git_merge_base_many()

Conflicts:
	src/notes.c

Errors were due to not including winsock2 early enough.

Precompile headers for MSVC.

When a configuration option is set, we didn't check to see whether
there was any escaping needed. Escape the available characters so we
can unescape them correctly when we read them.

Fix issue #763

make git_repository_init() value the core.logallrefupdates config entry 

This function has been available for some time, but never in a
header. Expose it so we can use it from outside the library.

git_status_file returns GIT_ENOTFOUND for files in "foo/" when .gitignore contains "foo bar.txt"

Fix filemode comparison in diffs

Missed a place that used this and missed git__isalpha

When checking for a drive letter on windows, instead of using
isalpha(), it is better to just check for a..z and A..Z, I think,
particularly because the MS isalpha implementation appears to
assert when given an 0xFF byte.