| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The diff --patch parser was missing some edge case where Git would
encode non-ASCII chars in path names as octals, but these weren't
decoded properly.
\360\237\222\251.txt
Decoded via utf-8, that will return:
💩.txt
|
|
Related to #450
|
|
|
|
Don't allow `, ` prefixes or suffixes in messages.
Fixes #438
|
|
|
|
|
|
|
|
Admittedly this fix is solely based on the documentation provided
for this parameter, which indicated a different intend than was
actually implemented. Also I don't believe doing this will cause
any harm.
As a special note: the call to `open(os.devnull, 'wb')` does not seem leak
the handle, apparently it is given as-is to the subprocess, which will then
close it naturally. This was tested using an interactive session via `htop`
on osx.
Fixes #437
|
|
Fixes #435
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
... 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
|
|
That way they are protected from regression.
Fixes #239
|
|
Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.
|
|
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
|
|
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
|
|
Next up is using threads
|
|
|
|
|
|
|
|
|
|
Kind of tackling the tasks step by step, picking low-hanging fruit first,
or the ones that everyone depends on
|
|
More to come, especially when it's about strings
|
|
There is more work to do though, as many imports are still incorrect.
Also, there are still print statements
|
|
This could however, introduce a chance of an assertion hitting once again
as it has been commented out for quite a long time. Now it's back in a changed form
though, and once again tries to make sure we get proper results
|
