$ repo sync
Traceback (most recent call last):
File "/media/git/aosp/.repo/repo/main.py", line 531, in <module>
_Main(sys.argv[1:])
File "/media/git/aosp/.repo/repo/main.py", line 507, in _Main
result = repo._Run(argv) or 0
File "/media/git/aosp/.repo/repo/main.py", line 180, in _Run
result = cmd.Execute(copts, cargs)
File "/media/git/aosp/.repo/repo/subcmds/sync.py", line 726, in Execute
mp.Sync_LocalHalf(syncbuf)
File "/media/git/aosp/.repo/repo/project.py", line 1327, in Sync_LocalHalf
self._InitWorkTree(force_sync=force_sync)
File "/media/git/aosp/.repo/repo/project.py", line 2477, in _InitWorkTree
raise e
error.GitError: --force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync .repo/manifests` to proceed.
Can someone confirm what the effects are of running repo sync --force-sync on the mirror?
Will this happen only for the mirror/manifest project, or for all projects specified in the mirror?