diff options
| author | Aymen Bouaziz <aymen.bouaziz@parrot.com> | 2016-10-25 18:03:51 +0200 |
|---|---|---|
| committer | Aymen Bouaziz <aymen.bouaziz@parrot.com> | 2016-10-28 14:29:57 +0200 |
| commit | 6c5944606af3c52626745b5256e9e5f0d5c362a2 (patch) | |
| tree | a34387f91d0a67c01455c2a211ae5401fe5a2bda /subcmds/smartsync.py | |
| parent | eceeb1b1f5edb0f42e690bffdf81828abd8ea7fe (diff) | |
| download | git-repo-6c5944606af3c52626745b5256e9e5f0d5c362a2.tar.gz | |
Fix checkout error when depth passed to repo init and revision is a sha1
Currently, if direct fetch of a sha1 is not supported by git server and
depth option is used, we fallback on syncing the upstream branch by
ignoring depth option.
This fallback doesn't work in next 2 cases:
(1) upstream attribute is not specified in manifest
(2) depth option is passed to repo init command
(not with clone-depth attribute in manifest)
This commit do the following:
- fixes (1) by updating condition used to apply fallback
first we retry with depth set to None, then by syncing all branches
- fixes (2) by passing depth as argument of _RemoteFetch() method
thus, its value is not set again to depth value passed to repo init
command when applying fallback
Change-Id: Ifd6fffafc49ba229df624b0d7b64c83d47619d17
Diffstat (limited to 'subcmds/smartsync.py')
0 files changed, 0 insertions, 0 deletions