dwim shorthand refspecs for fetch

don't use uninitialized struct stat in win32

cmake 2.6 parser bug workaround

Fix push for delete-only and add travis rules to test it

Create a test repository in the VM and set up git-daemon so we can
use it to test the push code.

For update and create commands where all the objects are known to
exist in the remote, we must send an empty packfile. However, if all
we issue are delete commands, no packfile must be sent.

Take this into consideration for push.

As git allows you to store shorthand refspecs in the configuration, we
need to do this ourselves.

Relax the ONELEVEL ref naming rules so the refspec parsing code can
ask for 'master' to be considered valid.

git_atomic_ssize for 64-bit atomics only on 64-bit platforms

Support more diff config options and use the config cache more

This makes diff use the cvar cache for config options where
possible, and also adds support for a number of other config
options to diff including "diff.context", "diff.ignoreSubmodules",
"diff.noprefix", "diff.mnemonicprefix", and "core.abbrev".

To make this natural, this involved a rearrangement of the code
that allocates the diff object vs. the code that initializes it
based on the combination of options passed in by the user and
read from the config.

This commit includes tests for most of these new options as well.

This is a conservative change, but it seemed like the only safe
thing to do -- i.e. clear the cvar cache when a config gets set.

This converts many of the config lookups that are done around the
library to use the repository config cache.  This was everything I
could find that wasn't part of diff (which requires a larger fix).

This adds a bunch of additional config values to the repository
config value cache and makes it easier to add a simple boolean
config without creating enum values for each possible setting.

Also, this fixes a bug in git_config_refresh where the config
cache was not being cleared which could lead to potential
incorrect values.

The work to start using the new cached configs will come in the
next couple of commits...

When case insensitive tree iterators were added, we started reading
the case sensitivity of the index to decide if the tree should be
case sensitive.  This is good for index-to-tree comparisons, but
for tree-to-tree comparisons, we should really default to doing a
case sensitive comparison unless the user really wants otherwise.

Remote refspecs minor fixes

64 bit atomic operations and shared cache memory usage

Added function to insert commit into pack

Make refcounting atomic