GitPython/git/test, branch 1.0.2

chore(flake8): unnused import

2016-02-07T11:01:12+00:00

fix(clone): call communicate if there is no progress handler

2016-02-07T10:56:19+00:00

Previously, it could have happened that pipes ran full, deadlocking the operation

Related to #72

DOC: minor typos

2016-01-08T19:29:46+00:00

fix(tree): remove Tree.cache - use IndexFile.write_tree() instead

2015-12-14T18:29:29+00:00

For more information, see CHANGES.rst

Fixes #369

fix(tree): show that fixing Tree.cache is not possible

2015-12-14T18:19:19+00:00

The problem is that a per-tree modification API cannot work properly, as the sorting is based
on full paths of all entries within the repository. This feat can only be achieved by the index,
which to my knowledge already does it correctly.

The only fix is to remove the misleading API entirely, which will happen in the next commit.

Related to #369

fix(tree): tree item sort now uses git-style

2015-12-13T12:10:33+00:00

Previously it was possible to generate trees which didn't
appear legit to git as gitpython's sorting was a simple alpha-numeric
sort. Git uses one that minimizes literal string comparisons though,
and thus behaves slightly differently sometimes.

Fixes #369

fix(config): ignore empty values in config file

2015-09-06T13:11:54+00:00

Similar to git, we now ignore options which have no value.
Previously it would not handle it consistently, and throw a parsing
error the first time the cache was built.

Afterwards, it was fully usable though.
Now we specifically check for the case of no-value options instead.

Closes #349

fix(compat): make test work with git >= 2.5

2015-08-29T14:25:40+00:00

fix(repo): fail loudly if worktrees are used

2015-08-29T14:20:28+00:00

As GitPython is in maintenance mode, there will be no new features.
However, I believe it's good idea to explicitly state we do not support
certain things if this is the case.

Therefore, when worktrees are encountered, we will throw an specific
exception to indicate that.

The current implementation is hacky to speed up development,
and increases the risk of failing due to false-positive worktree
directories.

Related to #344

fix(repo): use GitCmdObjectDB by default

2015-08-22T14:32:55+00:00

This should fix resource leaking issues once and for all.

Related #304