repo 1.12.25
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAABAgAGBQJVuUPMAAoJEGe35EhpKzgsaXQH/iuXG3mLh+VB9YKJ3DxP9xbH
dmndwbRjC8T1NcFOUmzgkik5MCitKNoO9HRb52fqCtaZ5+qfU3TzBZvZgNF0uwo8
S00CvAOfSkrE9H1XgNxKnuhGC5jJUmWaotN72ucPmvSEk8HqxTdWqTtRPkCIM6yu
WpNqNccS/InCuSsCwiNEXJVdhJGaUn0Ns5vb13Cx3O9MEtEuAdm/89TCOQ7/1M8j
6FamzIG1F4Sah6Nk7OfDS9PpuWJHYPqWEWlBvfPYOjghsvsEJPDoMFUXMgfqqu8M
56mevCkiEX4xH6u5hkNzi1mgeZAxWN5a73Ya81QRQ1hl8Wl0L47QjCiuvUBmIE4=
=haCa
-----END PGP SIGNATURE-----
Add option to correct gitdir when syncing

In some cases, a user may wish to continue with a sync even though
it would require overwriting an existing git directory. This behavior
is not safe as a default because it could result in the loss of some
user data, but as an optional flag it allows the user more flexibility.

To support this, add a --force-sync flag to the sync command that will
attempt to overwrite the existing git dir if it is specified and the
existing git dir points to the wrong obj dir.

Change-Id: Ieddda8ad54e264a1eb4a9d54881dd6ebc8a03833
2 files changed