mirror of
https://github.com/Dev-Wiki/git-repo.git
synced 2025-10-15 13:02:40 +08:00
14a6674e32b3000dbe8b7c96b0d1bb4fb0021720
Currently when doing a sync against a revision locked manifest, sync has no option but to fall back to sync'ing the entire refs space; it doesn't know which ref to ask for that contains the sha1 it wants. This sucks if we're in -c mode; thus when we generate a revision locked manifest, record the originating branch- and try syncing that branch first. If the sha1 is found within that branch, this saves us having to pull down the rest of the repo- a potentially heavy saving. If that branch doesn't have the desired sha1, we fallback to sync'ing everything. Change-Id: I99a5e44fa1d792dfcada76956a2363187df94cf1
Description
Languages
Python
99.2%
Shell
0.8%