On Feb 1, 2011, at 16:51, Nicolas Pitre wrote: > Also... people interested in Narrow clones are likely to be shallow > clone users too, right? Not necessarily. Many corporate repositories are huge (caused by the concept of 1 central repository with everything in it) and have tons of crud (like marketing materials, media-heavy powerpoint presentations). Here you really want a narrow clone (such as the sources of the project you're working on), but don't mind having the whole history. Looking at it from another angle: typically the whole history of a project is not much bigger than a check out, so it is fine to have a deep history. On the other hand, for these monster repositories one would typically do a narrow clone of only a single subdirectory that may be more than an order of magnitude smaller. These narrow clones are especially important for imports of unwieldy svn repositories where there is a large amount of unstructured branching. Regards, -Geert -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html