5 ms·
Yes, this is a more challenging and potentially risky one. I think you're taking the right approach by capturing the code and the history. In fact, I think you
by caseysoftware 11y ago
Yes, this is a more challenging and potentially risky one.
I think you're taking the right approach by capturing the code and the history. In fact, I think you're going above and beyond what most people should ask for or expect.
- _wmd 11y agoSeems you could just side-step SF directly in this case and contact one of their mirrors: http://sourceforge.net/p/forge/documentation/Join%20as%20a%20Mirror/ http://sourceforge.net/p/forge/documentation/Join%20as%20a%2... http://sourceforge.net/p/forge/documentation/Mirrors/ http://sourceforge.net/p/forge/documentation/Mirrors/ I bet at least one techie working at one of those organisations would lend a sympathetic ear to the effort, if you could find them edit: running 'rsync -r' on a local mirror shows 512,000 directories from a..ju, but only 43k files. Mirroring all the downloads should be easy