| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
This is a pre-emptive measure based on http://goo.gl/l74GC8 .
Related to #290
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, only program messages where forced to the C-locale, now
we force the entire program. That way, we should assure a remote
will not provide us with branch information in any other language but
english.
Related to #290
|
| | |
|
|\ \
| | |
| | | |
Fix type error (startswith expects bytes)
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| | |
As it seems to contain custom inforamtion that we want to keep.
Now we are appending to it ...
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* config parser now handles quoted values correctly. This doesn't hamper
multi-line support.
* added regression test to travis to assure we will be warned if we
rewrite and break the user's .gitconfig file
* only rewrite configuration files if we actually called a mutating
method on the writer. Previously it would always rewrite it.
Fixes #285
|
|\ \
| | |
| | | |
git-daemon test fixes
|
| | |
| | |
| | |
| | |
| | | |
add a GIT_PYTHON_TEST_GIT_DAEMON_PORT to set a port other than 9418,
for example for when you already have a daemon running on that port.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
No reason to expose a daemon to all interfaces when it is only used for
tests, which connect to localhost anyway.
I'd love to use localhost here instead, but the git-daemon man page points out:
If IPv6 is not supported, then --listen=hostname is also not
supported and --listen must be given an IPv4 address.
I don't know of a way to check if git has ipv6 support, but 127.0.0.1
should be around for the foreseeable future
|
|\ \
| | |
| | | |
Changelog typo
|
|/ /
| |
| | |
very small typo in changelog. Reop -> Repo
|
|\ \ |
|
| | |
| | |
| | |
| | | |
It expected to see major version 0 though.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |
| |
| |
| | |
We are not too good, but nothing to shy away from.
|
| |
| |
| |
| | |
Because there are none.
|
| |
| |
| |
| |
| | |
Just to declare the motivation behind this version jump, and state
it is similar to v0.3.7.
|
|/
|
|
|
|
| |
This is just me being honest to myself, after all, GitPython is already
version 3.0, considering that for me the leading zero was just
historical baggage.
|
|
|
|
| |
* milestone URL: http://goo.gl/HFaeZ4
|
|
|
|
|
|
| |
They didn't show up as code-block
Related to #256
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
It goes along with the new one advertising the GIT_SSH_COMMAND
environment variable.
Related to #256
|
| |
| |
| |
| |
| |
| | |
Also move untestable documentation out of test.
Related: #234, #242
|
| |
| |
| |
| | |
Related to #248
|
| |
| |
| |
| |
| |
| |
| | |
... 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
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
This should prevent a resource warning given in py3
Fixes #263
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
Previously it would always adjust your system path, which is bad
behaviour.
|
| |
| |
| |
| |
| | |
However, it doesn't reproduce on the latest version of GitPython.
Maybe it's on an older one.
|
| | |
|
|\ \
| | |
| | | |
Fix broken worktree path with submodules on Windows
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| | |
| | | |
Fix typo
|
|/ / |
|
|\ \
| | |
| | | |
Store path attribute on Diff object
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
If a file in a commit contains no changes (for example, if only the
file mode is changed) there will be no blob attached. This is
usually where the filename is stored, so without it, the calling
context can not tell what file was changed. Instead, always
store a_path and b_path on the Diff object so that information
is available.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In repositories like
> git branch -a
* test
> ls
test
`repo.iter_commits` failed due to an ambigous argument
(`'git rev-list test`).
Now this cannot happen anymore.
fixes #264
|
| |
| |
| |
| |
| | |
Related to #224
[ci skip]
|
| |
| |
| |
| |
| | |
Think about how expensive this single invisible character was, with
all the time and energy spent on it !
|
| |
| |
| |
| | |
Fixes #260
|
| |
| |
| |
| |
| |
| | |
While at it, all other invocations of .git in remote.py were reviewed
Fixes #262
|
|\ \
| | |
| | | |
BF: do not checkout master -- that ruins testing of PRs
|