tree af793b69bd9939ecbc42d390605c721e6ca97c08
parent 163fdbf2fd6ac8bb1f1e41fb74e68261badce32d
author Dan Willemsen <dwillemsen@google.com> 1438632713 -0700
committer Dan Willemsen <dwillemsen@google.com> 1438646056 -0700

Fix shallow clone behavior

The existing code here makes sure that switching clone-depth from on to
off actually causes the history to be fully restored. Unfortunately, it
does this by fetching the full history every time the fetch spec
changes. Switching between two clone-depth="1" branches will fetch far
more than the top commit.

Instead, when not using clone-depth, pass --depth=2147483647 to git
fetch so that it ensures that we have the entire history. That is
slightly less efficient, so limit it to only when there are shallow
objects in the project by checking for the existance of the 'shallow'
file.

Change-Id: Iee0cfc9c6992c208344b1d9123769992412db67b