delta/python-packages/gitpython.git/git/remote.py, branch 1.0.2

fix(cmd): prevent deadlock on clone/fetch/pull

2016-02-07T11:20:04+00:00

We keep stdout closed, which seems to have the side-effect of
stdout being connected to your TTY, in case you run a terminal.

However, this shold also prevent deadlocks, as only stderr is used.
The alternative would have been to try to fetch lines concurrently,
and we have been there.

For clone(), `communicate()` is used, and with some luck this will
just do the right thing. Even though last time I checked, it
didn't ... ? Lets see.

Stab at #72

chore(flake8): unnused import

2016-02-07T11:01:12+00:00

fix(remote): assure only repository configuration

2015-09-06T13:27:55+00:00

Previously it was possible for it to pick up non-repository
branch configuration, even though it was unlikely.

Closes #350

fix(cmd): work with py3

2015-07-03T14:43:51+00:00

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.

fix(cmd): don't open stdout when fetching

2015-07-03T13:37:29+00:00

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(remote): make assertion less verbose

2015-07-03T10:01:54+00:00

fix(remote): assert fetch respec is set

2015-06-10T14:59:00+00:00

It turns out we can't deal do fetches if no refspec is set as git
will change the format of the fetch return values, providing less
information than usual.

A test was added to show that such a case will fail, and an assertion
will assure we don't attempt to fetch/pull if there is no refspec
for 'fetch'.

Closes #296

fix(remote): don't close stdout on fetch/pull

2015-06-10T12:50:08+00:00

Reverted changes of `fe2fbc5~2`.

This caused `git-pull` to error, which now actually results in a fatal
error while fetching or pulling. Previously we simply didn't check
for this issue.

Now we are back to a `poll` based or threaded concurrent reading from
stdout and stderr to prevent a git process deadlock, and the
aforementioned error.

Related to #297

While parsing errors, also detecting lines starting with error:

2015-06-09T01:19:34+00:00

fix(remote): allow to raise during push/fetch

2015-04-08T09:00:32+00:00

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