From 9fbae711b76a4f2fa9345f43da6d2cdedd75d6c3 Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Tue, 20 Jan 2015 20:56:33 +0100 Subject: Greatly improved possible safety of Submodule.update(), which is used by 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. --- git/util.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'git/util.py') diff --git a/git/util.py b/git/util.py index 5385455a..8cab0b99 100644 --- a/git/util.py +++ b/git/util.py @@ -251,7 +251,10 @@ class RemoteProgress(object): message = message[:-len(done_token)] # END end message handling - self.update(op_code, cur_count, max_count, message) + self.update(op_code, + cur_count and float(cur_count), + max_count and float(max_count), + message) # END for each sub line return failed_lines -- cgit v1.2.1