summaryrefslogtreecommitdiffstats
path: root/man/repo-gitc-init.1
diff options
context:
space:
mode:
authorMike Frysinger <vapier@google.com>2021-11-05 15:22:01 -0400
committerMike Frysinger <vapier@google.com>2021-11-05 20:13:30 +0000
commit0531a623e19dd414840d062e19048a2ee5def235 (patch)
treea71c8b20c5ba9aa67df7568e7d8ca3b21496fa31 /man/repo-gitc-init.1
parent2273f46cb36893d20ab77d4dde1461d670d88e2c (diff)
downloadgit-repo-0531a623e19dd414840d062e19048a2ee5def235.tar.gz
sync: make --prune the default
If a remote deletes a ref, and it points to an object that doesn't exist locally, we can get into a bad state, and the only way for the user to recover is to run `repo sync --prune` (and to know that is the option they need). The error message is not helpful: fatal: bad object refs/remotes/cros/firmware-zork-13421.B-master error: https://chromium.googlesource.com/chromiumos/platform/ec did not send all necessary objects This situation can also come up when the remote renames refs in a UNIX FS incompatible way. For example, replacing refs/heads/foo with refs/heads/foo/bar. Also add a --no-prune option for users to disable the behavior. Bug: https://issuetracker.google.com/203366450 Change-Id: Icf45d838a10938feb091d29800f7e49240830ec3 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/322956 Reviewed-by: Andrew Lamb <andrewlamb@google.com> Tested-by: Mike Frysinger <vapier@google.com>
Diffstat (limited to 'man/repo-gitc-init.1')
0 files changed, 0 insertions, 0 deletions