| Age | Commit message (Collapse) | Author |
|---|
|
This will make usage of the `NullHandler` possible in python 2.6
and below.
|
|
|
|
The previous patch failed to update the expected number of op_codes,
which would result in an exception when creating an instance of
RemoteProgress. This patch corrects the value to the new expected number
of op_codes (8)
|
|
When running a long running operation (such as a clone on a large repo),
Git may return a message indicating that it is 'Finding sources'. Since
there is no bit field value for this message, this causes a large amount
of error messages to be emitted to stderr.
This patch fixes this by adding another bit field value for this
message, FINDING_SOURCES. Derived classes can look for this op_code and
handle it appropriately.
|
|
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
|
|
When pushing/pulling, we ignore errors unless it's exit code 128.
The reason for this is now made explicit to make clear that issues
are handled by PushInfo flags accordingly.
Related #271
|
|
Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.
|
|
The latter happened as now BadName is thrown, instead of BadObject.
Changes.rst was marked accordingly
|
|
default.
Previously, the implementation would gladly reset new commits in submodules,
and/or reset a dirty working tree.
Now the new force_reset/force flag has to be specified explicitly to get back
to the old behaviour.
All submodule tests except for one are working.
|
|
Assured unicode values are supported when reading the configuration,
and when getting author/committer information from the environment.
Fixes #237
|
|
Fixes #7
[ci skip]
|
|
|
|
|
|
|
|
Next up is using threads
|
|
|
|
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
|
|
Commandline was
autopep8 -j 8 --max-line-length 120 --in-place --recursive --exclude "*gitdb*,*async*" git/
|
|
W291 trailing whitespace
|
|
E201 whitespace after '('
E202 whitespace before ')'
E203 whitespace before ':'
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E227 missing whitespace around bitwise or shift operator
E228 missing whitespace around modulo operator
E231 missing whitespace after ','
E241 multiple spaces after ','
E251 unexpected spaces around keyword / parameter equals
|
|
E301 expected 1 blank line, found 0
E302 expected 2 blank lines, found 1
E303 too many blank lines (n)
|
|
W191 indentation contains tabs
E221 multiple spaces before operator
E222 multiple spaces after operator
E225 missing whitespace around operator
E271 multiple spaces after keyword
W292 no newline at end of file
W293 blank line contains whitespace
W391 blank line at end of file
|
|
johnsca-sf-master
Conflicts:
git/cmd.py
git/objects/commit.py
git/objects/fun.py
git/objects/util.py
git/remote.py
git/repo/base.py
git/test/lib/helper.py
git/test/test_commit.py
git/test/test_fun.py
git/util.py
|
|
Changed motivated by https://github.com/gitpython-developers/GitPython/pull/52
|
|
https://github.com/gitpython-developers/GitPython/commit/f362d10fa24395c21b1629923ccd705ba73ae996
Related to #43
|
|
probably a good idea to go a little more pep8 (and fix sins of my youth ;) )
|
|
The `finalize_process` method was moved but this import wasn't carried with it.
|
|
|
|
read-only files to be removed on windows as well
|
|
partial or intermixed lines from the pipe. This really shouldn't be, but its windows so it happens
|
|
functionality
|
|
critical bug which caused packed-ref files to be written with native line endings, which made git fail to parse it. I wonder why I never noticed this before, or ignored it. Unbelievable \!
|
|
|
|
is push, fetch, pull and clone. This allows progress information to be sent in newer git versions without breaking older ones (ideally)
|
|
|
|
the error was caused by PySide which, when instantiating a QApplication, changed the signal handlers to interrupt, instead of retry operating system calls, which caused git-python to fail subsequently. signal.siginterrupt can be used to fix this behaviour after an QApplication was instatiated.
|
|
platform.system makes a system call itself
|
|
specific subprocess bug occurs.
|
|
adjusted
|
