You are making the problem sounds worse than it is.
I'm not sure what you mean but those 200Mb took 2h30 yesterday afternoon,
tonight, less than 15mn, I'm not sure it came from the apache servers but
because it already appened before, I suspected it, so maybe I made noise but
better that and realize it wasn't a permanent problem than having troubles
all the time.
Sparse checkout does help doesn't it?
Yes, it helps anyway, because once filtered, the git operations are quicker
than if they have to do what they have to do on the entire tree.
-Fred
-----Message d'origine-----
From: Om
Sent: Monday, March 18, 2013 3:59 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
'actually, you can argue that the fetch size is far smaller (about 200 Mb)
than the result of the checkout (about 2.6Gb)'
That is exactly what I am saying. You are making the problem sounds worse
than it is.
Sparse checkout does help doesn't it?
