An upstream tree I'm mirroring with git-p4 has decided to start checking in large tarballs (150MB) periodically. It's basically a prebuild version of some firmware needed to run the rest of the software. Git doesn't seem to have any problem with these tarballs (and is using a lot less space than P4), but I have a feeling we might start running into problems when things get real big. Does anyone have experience with packs growing beyong several GB? Aside from that, is there an easy way to prune out the old history from a working tree? I'd like something like what 'git clone --depth n' would produce, and I suppose I could do the clone and then pivot the trees. I mainly don't want to be rewriting history, just making parts inaccessible. Thanks, David Brown - 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
