| Age | Commit message (Collapse) | Author |
|
In response to
https://github.com/gitpython-developers/GitPython/pull/408/files/5de21c7fa2bdd5cd50c4f62ba848af54589167d0..aae2a7328a4d28077a4b4182b4f36f19c953765b#r59722704
|
|
Just to get the tests green again for py2.7.
Deleting the test isn't the right way to do it, but the one of a
maintainer who wants to spend no more time than possibly necessary.
|
|
|
|
Previously travis would fail to clone the special testing repository
as SSH access requires a deploy key to be set. The latter has been
configured and is now added in clear-text.
This is save as it is only good for read-only access to a test
repository, mis-use cannot happen that way.
|
|
Related to #301
|
|
As it seems to contain custom inforamtion that we want to keep.
Now we are appending to it ...
|
|
* config parser now handles quoted values correctly. This doesn't hamper
multi-line support.
* added regression test to travis to assure we will be warned if we
rewrite and break the user's .gitconfig file
* only rewrite configuration files if we actually called a mutating
method on the writer. Previously it would always rewrite it.
Fixes #285
|
|
original HEAD
|
|
... as we are now running out of file handles.
Previously, it worked ... and gitpython didn't change
|
|
|
|
At least leakage is considerably reduced.
Additionally, a test-case was added which triggers failure if auto-disposal
of resources wouldn't work.
Fixes #60
|
|
Fixes #177
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... and be able to run performance tests independently of the chosen performance test repo
Now all tests run fine locally
|
|
* travis configuration adjusted to hopefully work better than before
Performance traversal still fails when using git-python as standard repository.
It naturally wants a larger one. On travis these tests are skipped though.
|
|
* GIT_PYTHON_TRACE now behaves correctly for fetch, and pull (i.e. if as_process is used)
* Improved parsing of fetch head information
However, there is still a messy bit that tries to bring together fetch progress information
with fetch head information. Even though it works now, an alternative implementation should
be attempted.
|
|
|
|
from its own repo, tags are known to be stable
|
|
If not, pip install should do the job
|
|
|