| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
If the file was not present, the mode seen in a diff can be legally '0',
which previously caused an assertion to fail for no good reason.
Now the assertion tests for None instead.
Closes #323
|
| |
|
|
|
|
| |
There is simply no excuse to doing that.
Closes #330
|
| |\
| |
| |
| |
| | |
Be explicit about usage of commit of head-ref in index diff call.
There is no need to do this, but it won't hurt either.
|
| |/ |
|
| |\
| |
| | |
Ensure file resources are released
|
| |/ |
|
| |\
| |
| | |
gic {init,clone} --separate-git-dir is supported only since 1.7.5
|
| |/
|
|
|
| |
Without this commit the update() function of a submodule does not work
in CentOS 6.
|
| |\
| |
| | |
Implement is_ancestor
|
| |/
|
|
|
| |
Wrap `git merge-base --is-ancestor` into its own function because it acts
as a boolean check unlike base `git merge-base call`
|
| |
|
|
|
|
| |
I knew that flake would eventually get me, especially when least
suspected.
This time it's even useful, as it is a non-whitespace related issue.
|
| |
|
|
|
| |
It was a left-over of some prior hacking that was not removed by
accident.
|
| |
|
|
|
|
|
| |
I have no idea why PY3 requires such a mess of encoding/decoding
statements, but let's just be happy it works.
Also let's be sure I never ever write python code again ... EVER.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* untracked_files could, if there were spaces in the path returned,
re-rencode the previously decoded unicode string thanks to a
`decode("string_escape")` call. Now re-encode into utf-8 afterwards
- added test to assure this works indeed
* IndexFile.add() didn't handle unicode correctly and would write
broken index files. The solution was to compute the path length after
encoding it into utf-8 bytes, not before ... .
Closes #320
|
| |\
| |
| | |
Always add '--' to git reset
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a git repo has the misfortune to have a file with the name "HEAD"
at the root level of the repo, git will return an error because it
is unsure whether the file or ref is meant:
File "/usr/local/lib/python2.7/dist-packages/git/refs/head.py", line 81, in reset
self.repo.git.reset(mode, commit, add_arg, paths, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/git/cmd.py", line 440, in <lambda>
return lambda *args, **kwargs: self._call_process(name, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/git/cmd.py", line 834, in _call_process
return self.execute(make_call(), **_kwargs)
File "/usr/local/lib/python2.7/dist-packages/git/cmd.py", line 627, in execute
raise GitCommandError(command, status, stderr_value)
GitCommandError: 'git reset --hard HEAD' returned with exit code 128
stderr: 'fatal: ambiguous argument 'HEAD': both revision and filename
Use '--' to separate filenames from revisions'
Implement its suggested fix by always passing '--' as an argument to
"git reset". It is fine to pass it with no file specifiers afterwords.
In that case, git knows that "HEAD" is always meant as the ref.
|
| |\ \
| |/
|/| |
typo in submodules api documentation
|
| |/ |
|
| |\
| |
| | |
Feature: Make commits with custom `author_date` and `commit_date` (closes #315)
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Correct doc errors
|
| |/
|
|
|
|
|
|
|
| |
revA..revB → revA...revB (three instead of two dots) [base.py, line
467](https://github.com/gitpython-developers/GitPython/blob/master/git/repo/base.py#L467)
rorepo is a ~~a~~ Repo instance [test_docs.py, line
21](https://github.com/gitpython-developers/GitPython/blob/master/git/test/test_docs.py#L21)
closes #314
|
| |\
| |
| | |
Fix typo
|
| |/ |
|
| |\
| |
| | |
care tilde in include.path config
|
| | | |
|
| |/ |
|
| |
|
|
| |
Seems like OSX is somewhat special here ... .
|
| |
|
|
|
|
| |
Fixed additional test which seems to have different outcomes depending
on the interpreter. This just makes it work withouth attempting
to find the root cause of the issue.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Previously travis would fail to clone the special testing repository
as SSH access requires a deploy key to be set. The latter has been
configured and is now added in clear-text.
This is save as it is only good for read-only access to a test
repository, mis-use cannot happen that way.
|
| |
|
|
| |
Related to #301
|
| |
|
|
|
|
|
| |
This allows us to use the main thread to parse stderr to get progress,
and resolve assertion failures hopefully once and for all.
Relates to #301
|
| |
|
|
|
| |
Test was adjusted as well to parse only a single file which simulates
stderr output.
|
| | |
|
| |
|
|
|
|
| |
* Previously we could fail to parse the last line within a read buffer,
which is now fixed.
* Added a test to verify our *slow* line parsing works as expected.
|
| |\
| |
| | |
Add env parameter to Repo.clone_from() for setting environment variables
|
| |/
|
|
|
|
|
| |
Adds the optional keyword parameter env to Repo.clone_from(). The parameter
is a dictionary containing the desired environment variables for the git
clone invocation. The environment is applied to the temporary Git instance
before calling Repo._clone().
|
| |\
| |
| | |
Fix docstring of Repo.clone_from()
|
| |/ |
|
| |
|
|
|
|
|
| |
It shows that the previous implementation was never really working on
linux, and thus failed on travis as well for good reason.
Closes #303
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
When expanding directories, check if it is a symlink and don't expand
them at all.
Previously, we followed symlinks and expanded their contents, which
could lead to weird index files.
Fixes #302
|
| |\ |
|
| | |
| |
| |
| |
| | |
This will make usage of the `NullHandler` possible in python 2.6
and below.
|
| |/
|
|
|
|
|
|
| |
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.
|
| |\
| |
| | |
support passing odbt for using with Repo
|
| | | |
|
| | | |
|
