| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
In response to
https://github.com/gitpython-developers/GitPython/pull/408/files/5de21c7fa2bdd5cd50c4f62ba848af54589167d0..aae2a7328a4d28077a4b4182b4f36f19c953765b#r59722704
|
|
|
|
|
|
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
|
|
They didn't show up as code-block
Related to #256
|
|
|
|
It goes along with the new one advertising the GIT_SSH_COMMAND
environment variable.
Related to #256
|
|
... 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
|
|
|
|
Also move untestable documentation out of test.
Related: #234, #242
|
|
Fixes #246
|
|
However, I kept information on how to achieve the same thing with
`custom_environment()` in the test.
Related to #234
|
|
Need latest master to proceed with test
Conflicts:
doc/source/tutorial.rst
|
|
Renamed context manager 'with_environment' to 'custom_environment'.
On my way to implement sshkey test.
|
|
That way they are protected from regression.
Fixes #239
|
|
|
|
Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.
|
|
GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations.
Related to #239
|
|
Now travisci tests should work once again.
Related to #239
|
|
The latter happened as now BadName is thrown, instead of BadObject.
Changes.rst was marked accordingly
|
|
Additionally, for this and future examples, there is a test_doc.py
suite to contain all code mentioned in the docs. That way, we know
if things stop working.
Fixes #236
|
|
Fixes #235
[ci skip]
|
|
A test verifies it's truly working.
Related to #238
|
|
This allows sub-trees to be archived as well, and makes `.archive()`
feature complete.
Fixes #67
|
|
Fixes #169
|
|
However, it does so only on posix. The test-case will run on posix only
as well.
Please note that in theory, even on windows we will attempt to run hooks,
even though I am not sure that this will actually work.
Fixes #81
|
|
Now by default, we will not walk up the directory structure and possibly find
git directories that the user didn't intend to find.
If required, that kind of behaviour can be turned back on.
Fixes #65
|
|
Fixes #34
|
|
Fixes #36
|
|
firm1-commit_by_actor
|
|
|
|
Next up is using threads
|
|
|
|
|
|
|
