diff options
| author | Kaushik Lingarkar <kaushikl@qti.qualcomm.com> | 2025-04-07 17:08:07 -0700 |
|---|---|---|
| committer | LUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com> | 2025-04-17 11:46:11 -0700 |
| commit | a94457d1ce04b31f63734a8c8a1dc668668af39d (patch) | |
| tree | 1fb0f11469b63223a083addc23bd44d848747783 /subcmds/rebase.py | |
| parent | 97dc5c1bd9527c2abe2183b16a4b7ef037dc34a7 (diff) | |
| download | git-repo-a94457d1ce04b31f63734a8c8a1dc668668af39d.tar.gz | |
Fallback to full sync when depth enabled fetch of a sha1 fails
In sha1 mode, when depth is enabled, syncing the revision from
upstream may not work because some servers only allow fetching
named refs. Fetching a specific sha1 may result in an error like
'server does not allow request for unadvertised object'. In this
case, attempt a full sync with depth disabled.
Bug: 410825502
Change-Id: If51bcf18b877cd9491706f5bc3d6fd13c0c3d4f3
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/468282
Commit-Queue: Kaushik Lingarkar <kaushikl@qti.qualcomm.com>
Tested-by: Kaushik Lingarkar <kaushikl@qti.qualcomm.com>
Reviewed-by: Gavin Mak <gavinmak@google.com>
Reviewed-by: Mike Frysinger <vapier@google.com>
Diffstat (limited to 'subcmds/rebase.py')
0 files changed, 0 insertions, 0 deletions