Felix>My problem here is, that I sometimes checkout a historic version and Felix>can't get away from it, as git complains that the files have changed
Please provide the exact steps to reproduce. So far git checkout v213 V2_13; git checkout master; works for me just fine when using Windows/macOS Felix>Yes, for future versions of our source, that would be a nice enhancement. I've kept all the css, js, etc files. I've ran pngquant (2.12.2, January 2018, libpng 1.6.37) through all the historical commits. It results in 53MiB repository (it was 40 when historical png were just removed). Hopefully multi-megabyte files won't be pushed to the repository, and I hope JS/CSS dependencies would be managed though Webpack (or whatever). I guess "component UI" images can be generated automatically at build time, however that's a side discussion. The updated repository: https://github.com/apache/jmeter SVN references are good, Git references are good. Travis build passes ( https://travis-ci.org/apache/jmeter/builds/543612661 ) Note: migrate procedure is updated. The key change is you need my release of BFG. See https://github.com/vlsi/jmeter-git-cleanup/tree/v2.1.1/clean_fork PS In fact, references to "old" Git commit ids would be more or less useless without "old Git repo". I just thought we could create a "readonly" Git repo, and use links that point to commits in that repository instead of just current "commit ids". Any thoughts on that? It can be done quite easily (I use my own build of BFG anyway, so I can add http://github.com/apache/jmeter-svn-mirror/... there) On the other hand, I'm +-0 about that since I think the new Git repo is just fine, and just commit id is sufficient for the search purposes. Vladimir >
