summaryrefslogtreecommitdiffstats
path: root/subcmds/sync.py
diff options
context:
space:
mode:
authorShawn O. Pearce <sop@google.com>2009-04-18 10:39:28 -0700
committerShawn O. Pearce <sop@google.com>2009-04-18 10:39:28 -0700
commit336f7bd0ed70f5ee2595463b6bd8dd277e90c833 (patch)
tree4854b1808bcda18221e097a69c993c4a0cf6137a /subcmds/sync.py
parent2810cbc7784e9a21e7001c31b65af94fd9ba7a5b (diff)
downloadgit-repo-336f7bd0ed70f5ee2595463b6bd8dd277e90c833.tar.gz
Avoid git fork on the common case of repo not changing
Usually repo is upgraded only once a week, if that often. Most of the time we invoke HasChanges on the repo project (or even on the manifest project) the current HEAD will resolve to the same SHA-1 as the remote tracking ref, and there are therefore no changes. Signed-off-by: Shawn O. Pearce <sop@google.com>
Diffstat (limited to 'subcmds/sync.py')
0 files changed, 0 insertions, 0 deletions