On Feb 3, 2011, at 12:39, Jonathan Nieder wrote: > Geert Bosch wrote: > >> These narrow clones are especially important for imports of unwieldy >> svn repositories where there is a large amount of unstructured >> branching. > > Wouldn't a more careful import be a better solution to that problem? Yes. > Practically speaking, I'd rather work with an enormous svn repo like > that by using git-svn to extract subsets than with a botched import > that treats it as one huge (git-managed) project. Practically speaking, I don't always have a say in the organization of repositories that I have to work with. Some would rather spend 30+ days of CPU time to import an entire SVN repository with branch forests straight into git than considering organization. Of course the resulting git repository will be less than useful. And that's where the narrow clone comes in handy... -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