When we discover that we want to keep a negative rule, make sure to
clear the error variable, as it we otherwise return whatever was left by
the previous loop iteration.

Our doc parser really wants the types to be declared in the header it's
reading.

Improve server error reporting

This can be used by tools to show mesages about failing to communicate
with the server. The error message in this case will often contain the
server's error message, as far as it managed to send anything.

When we fail to read from stdout, it's typically because the URL was
wrong and the server process has sent some output over its stderr
output.

Read that output and set the error message to whatever we read from it.

Use a diff for iteration in index_update_all and index_add_all

Provide error messages for git_path_direach operations

We set an error if we get an error when reading, but we don't bother
setting an error message for write failing. This causes a cryptic error
to be shown to the user when the target filesystem is full.

Now that `git_path_direach` lets us specify an error message to report,
set an appropriate error message while linking.

This function deals with functions doing IO which means the amount of
errors that can happen is quit large. It does not help if it always
ovewrites the underlying error message with a less understandable
version of "something went wrong".

Instead, only use this generic message if there was no error set by the
callback.

Updated dlibgit link.

Bring Early EOF message in line with the other two

Without this option, we would not be able to catch exec bit changes.

Instead of going through each entry we have and re-adding, which may not
even be correct for certain crlf options and has bad performance, use
the function which performs a diff against the worktree and try to add
and remove files from that list.

Refactor so we look like the code we're replacing, which should also
allow us to more easily inplement add-all.

We currently iterate over all the entries and re-add them to the
index. While this provides correctness, it is wasteful as we try to
re-insert files which have not changed.

Instead, take a diff between the index and the worktree and only re-add
those which we already know have changed.

Add tests for and fix push negotiation notification

There was a copypasta error and the source and destination IDs were
reversed.

The functionality was meged without including tests, so let's add them
now.

Attributes: don't match files for folders

Use the packbuilder in local push

Show progress during packing for the local transport

odb: make the writestream's size a git_off_t

The interesting one is the notification macro, which was returning
directly on a soft-abort instead of going through the cleanup.

This is useful to send to the client while we're performing the work.

The reporting function has a force parameter which makes sure that we
do send out the message of 100% completed, even if this comes before the
next udpate window.

Set a callback for the packbuilder so we can send the sideband messages
to the caller, formatting them as git would.

This lets us see what the server (or libgit2 locally) is doing, rather
than having to stare at a non-moving screen.

index: make the entries have more accurate sizes

Get rid of libssh2 embedding

submodule: add test initialising and cloning a repo

odb: reverse the default backend priorities

A couple of tests use the wrong remote to push to. We did not notice up
to now because the local push would copy individual objects, and those
already existed, so it became a no-op.

Once we made local push create the packfile, it became noticeable that
there was a new packfile where it didn't belong.

Instead of copying each object individually, as we'd been doing, use the
packbuilder which should be faster and give us some feedback.

While performing this change, we can hook up the packbuilder's writing
to the push progress so the caller knows how far along we are.