Dan Willemsen eeab6860f1 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
2015-08-03 16:54:16 -07:00
2012-11-14 11:38:57 +09:00
2013-03-08 01:18:08 +00:00
2015-03-28 21:12:27 +00:00
2008-10-21 07:00:00 -07:00
2015-06-04 00:21:16 +00:00
2015-06-04 00:22:23 +00:00
2013-11-21 06:03:22 +00:00
2011-09-19 14:52:57 -07:00
2015-08-03 16:54:16 -07:00
2014-01-30 15:17:09 -08:00
Description
No description provided
Apache-2.0 35 MiB
Languages
Python 99.1%
Shell 0.9%