| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Without this commit the update() function of a submodule does not work
in CentOS 6.
|
| |
|
|
|
|
|
|
|
|
| |
When the code is run without setting up loggers, the loggers have no
handlers for the emitted messages. The logging module displays:
`No handlers could be found for logger "git.cmd"` on the
console. By adding a NullHandler (a no-op) the message disappears,
and doesn't affect logging when other handlers are configured.
|
|
|
|
|
|
|
|
| |
On Windows, `repo.create_submodule(...)` failed because git didn't recognize
the worktree path set in `.git/modules/sub/config` (`fatal: bad config file
line 6 in ./config`). This commit makes `_write_git_file_and_module_config`
convert the worktree path to the linux format (forward slashes) which git
recognizes.
|
| |
|
|
|
|
|
|
|
| |
As I am pretty sure to have tested it with 1.7.0, I assume they
added the git file feature somewhere between .0 .10.
Fixes #252
|
|
|
|
| |
It's new in the latest version of flake - thanks travis for letting me know.
|
|
|
|
|
|
| |
That, over time, could have caused slow downs due to file-system hassle.
Fixes #258
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Previously we could try to remove the branch we are on.
Of course, we have a test-case elaborate enough to verify we don't
destroy changes in submodules accidentally. Therefore I am confident
that this implementation is correct.
Fixes #49
|
|
|
|
|
| |
The latter happened as now BadName is thrown, instead of BadObject.
Changes.rst was marked accordingly
|
|
|
|
| |
Fixes #50
|
|
|
|
|
|
|
|
| |
was set before.
That way, you don't always have to keep the parent commit uptodate when changing the
repo, which can lead to errors which are hard to debug and make no sense to the user,
who previously never set parent_commit (yet it matters thanks to the cache).
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
path
Fixes #238
|
|
|
|
|
|
| |
A test verifies it's truly working.
Related to #238
|
|
|
|
|
|
|
| |
Improved a test to assure multiple update(init=False|True) calls don't
throw.
Fixes #93
|
|
|
|
|
|
|
|
| |
After all, it was easier than expected. It seems that previous assertions
the test made should have never been true to begin with. Thus we might
have improved the test thanks to our improved implementation.
Fixes #233
|
|
|
|
|
|
| |
This also means that now we seem to be able to properly handle .git files in submodules
Related to #233
|
|
|
|
|
| |
The root-submodule test is still failing though, this time even earlier
than before
|
|
|
|
| |
A simple test verifies this at least.
|
|
|
|
|
| |
However, a simple test-case still fails for reasons not yet understood.
There is more to be fixed here - .remove() still fails.
|
|
|
|
|
|
|
| |
There is some more work to do, as renames and updates still have to be
adjusted accordinlgy.
Relates #233
|
|
|
|
|
|
| |
It actually revealed a bug in the implementation of Submodule.add,
which just showed in python 3 for the wrong reasons. Thankfully,
failing tests after all allowed to get this issue fixed ... .
|
|
|
|
|
|
|
|
|
|
| |
string.
Previously, it would say it can handle absolute module paths, but didn't
actually do so.
A test-case was improved to check for this case.
Fixes #161
|
|
|
|
|
|
|
| |
Adjusted code to not check for .gitmodules existence anymore, we will
deal with it.
Fixes #117
|
|
|
|
|
|
| |
This is verified by the respective test.
Fixes #117
|
| |
|
|
|
|
| |
Now it's about going through PY3 issues
|
|
|
|
|
|
| |
However, StringIO really is ByteIO in most cases, and py2.7 should
run but doesn't.
This should be made work first.
|
|
|
|
| |
More to come, especially when it's about strings
|
|
|
|
| |
All performance tests still print to stderr, but do so in a py3 compatible way
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
type in python.
The latter will break code that assumes it will get a string.
|
|
|
|
| |
probably a good idea to go a little more pep8 (and fix sins of my youth ;) )
|
|
|
|
| |
read-only files to be removed on windows as well
|
|
|
|
| |
correctly now - previously it would pass the full path of the branch, which in fact didn't work, unless the default branch is used to which it will default. The bug wasn't noticed because of this
|
|
|
|
| |
into that, or at least triggered it
|
|
adjusted
|