| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Vastly improved windows support and a few bugfixes.
|
|
|
|
|
|
+ Some cases had restructuring of code.
|
|
This has been the case for Windows as well, and is now
made official.
Certain tests already fail on windows, for example.
|
|
Fixes #508
|
|
It's not optimal, as we can now return one of two types
which are only compatible in the most basic ways.
However, it is better than before, I presume.
Fixes #510
|
|
It's entirely untested if this repo still does the right thing,
but I'd think it does.
Fixes #504
|
|
As TagObjects can point to other TagObjects, we need
to keep going in order to resolve the final commit.
Fixes #503
|
|
|
|
That way, we do not have to figure the change type out by
examining the diff object.
It's implemented in a way that should yield more desireable results
as we keep the change-type that git is providing us with.
Fixes #493
|
|
This mentions the instructions of what was discussed in #489.
|
|
|
|
|
|
Previously, the following fields on Diff instances were assumed to be
passed in as unicode strings:
- `a_path`
- `b_path`
- `rename_from`
- `rename_to`
However, since Git natively records paths as bytes, these may
potentially not have a valid unicode representation.
This patch changes the Diff instance to instead take the following
equivalent fields that should be raw bytes instead:
- `a_rawpath`
- `b_rawpath`
- `raw_rename_from`
- `raw_rename_to`
NOTE ON BACKWARD COMPATIBILITY:
The original `a_path`, `b_path`, etc. fields are still available as
properties (rather than slots). These properties now dynamically decode
the raw bytes into a unicode string (performing the potentially
destructive operation of replacing invalid unicode chars by "�"'s).
This means that all code using Diffs should remain backward compatible.
The only exception is when people would manually construct Diff
instances by calling the constructor directly, in which case they should
now pass in bytes rather than unicode strings.
See also the discussion on
https://github.com/gitpython-developers/GitPython/pull/467
|
|
|
|
Relates to #446
|
|
|
|
|
|
This catches the case where the matched line contains "(" or ")"
characters.
|
|
|
|
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
|
|
|
|
|
