Currently it is not possible to have a shallow depth of just 0, i.e. only one commit in that repository after cloning. The minimum number of commits is 2, caused by depth=1.
I had no good idea how to add this behavior to git clone as the depth variable in git_transport_options struct (file transport.h) uses value 0 for another meaning, so it would have need changes at all places, where the transport options depth is being used (e.g. fetch) So I documented the current behavior, see attached patch. Stefan Beller (1): Documentation on depth option in git clone. Documentation/git-clone.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- 1.8.1.80.g3e293fb.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
