summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJosip Sokcevic <sokcevic@google.com>2023-02-01 14:51:52 -0800
committerJosip Sokcevic <sokcevic@google.com>2023-02-01 23:38:52 +0000
commitdccf38e34f5ce48a8583df320d7c5e203d2a9cf2 (patch)
treebbd4cdb60aae1d0290da04f76641333fd7101e9c
parent7f44d366d016039c32c374db27e9956919fe2dfb (diff)
downloadgit-repo-dccf38e34f5ce48a8583df320d7c5e203d2a9cf2.tar.gz
Update sync progress
repo sync progress bar is misleading. Many bug reports mentioned that repo is stuck at the repo that is currently displayed in the progress bar. Repo sync actually shows what repository is the last processed. This change makes that obvious. Change-Id: I962bf0bc65af7ac0ed98db86e9144f07d9e1f96f Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/357134 Reviewed-by: Joanna Wang <jojwang@google.com> Tested-by: Josip Sokcevic <sokcevic@google.com>
-rw-r--r--subcmds/sync.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/subcmds/sync.py b/subcmds/sync.py
index 1c38d266..4b7e81df 100644
--- a/subcmds/sync.py
+++ b/subcmds/sync.py
@@ -544,7 +544,7 @@ later is required to fix a server side protocol bug.
544 ret = False 544 ret = False
545 else: 545 else:
546 fetched.add(project.gitdir) 546 fetched.add(project.gitdir)
547 pm.update(msg=project.name) 547 pm.update(msg=f'Last synced: {project.name}')
548 if not ret and opt.fail_fast: 548 if not ret and opt.fail_fast:
549 break 549 break
550 return ret 550 return ret