For more information, see CHANGES.rst

Fixes #369

This should fix resource leaking issues once and for all.

Related #304

Previously timezones which were not divisable by 3600s would be
parsed correctly, but would serialize into a full hour, rounded up.

Now floating point computation is used which fixes the issue.

Related to #336

very small typo in changelog. Reop -> Repo

Just to declare the motivation behind this version jump, and state
it is similar to v0.3.7.

* milestone URL: http://goo.gl/HFaeZ4

... if it is not found. Previously, especially on windows, this wasn't
explicit.

Fixes #248, affects #126

Do not swallow non-zero exit status during push and fetch unless
we managed to parse head information.

This behaviour will effetively handle cases were no work was done
due to invalid refspecs or insufficient permissions.

Fixes #271

It turned out that the index is not actually corrupted, which is good
news. What happens is that `git` writes `TREE` extension data into the
index, which causes it to write out the given tree *as is* next time
a `git commit` is executed. When using `git add`, this extension data
is maintained automatically. However, GitPython doesn't do that ... .
Usually this is no problem at all, as you are supposed to use
`IndexFile.commit(...)` along with `IndexFile.add(...)`.

Thanks to a shortcoming in the GitPython API, the index was
automatically written out whenever files have been added, without
providing control over whether or not *extension data* will be
written along with it.

My fix consists of an additional flag in `IndexFile.add(...)`, which
causes extension data not to be written by default, so commits can be
safely done via `git commit` or `IndexFile.commit(...)`.

However, this might introduce new subtle bugs in case someone is
relying on extension data to be written. As this can be controlled
through the said flag though, a fix is easily done in that case.

Fixes #265