From de9a6bb0c8931e7f74ea35edb372e5ca7d0a5047 Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Sat, 3 Jan 2015 14:34:39 +0100 Subject: Various fixes and improvements * GIT_PYTHON_TRACE now behaves correctly for fetch, and pull (i.e. if as_process is used) * Improved parsing of fetch head information However, there is still a messy bit that tries to bring together fetch progress information with fetch head information. Even though it works now, an alternative implementation should be attempted. --- git/cmd.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'git/cmd.py') diff --git a/git/cmd.py b/git/cmd.py index f4d23002..bfdefb17 100644 --- a/git/cmd.py +++ b/git/cmd.py @@ -333,7 +333,7 @@ class Git(LazyMixin): :note: If you add additional keyword arguments to the signature of this method, you must update the execute_kwargs tuple housed in this module.""" - if self.GIT_PYTHON_TRACE and not self.GIT_PYTHON_TRACE == 'full': + if self.GIT_PYTHON_TRACE and (self.GIT_PYTHON_TRACE != 'full' or as_process): print ' '.join(command) # Allow the user to have the command executed in their working dir. -- cgit v1.2.1