Open StephenCarlson opened 3 years ago
Quick update on this: I've made a development branch and played with updating using this merge mechanism, and it works. Also, the current repo size including the .git
folder is over 300MB, which is annoying. The fears I had as articulated in May are becoming real; that despite my efforts to minimize repo inflation through carefully commits and management, the baggage and burden of file history is starting to snowball. How do I fix this?
Git is not the optimal version control system for hardware projects, as I understand it. Cloning or forking the repo incurs the burden of downloading all history, which when looking at STL files that are a handful of MB each, and dozens of STL files, each with several versions, and it blows up to hundreds of MB. Maybe I'm forgetting that Git does a form of compression? Anyhow, there are probably ways to reduce the burden by branching, or otherwise optimizing the history, if not deleting it somehow. As the project is polished and improved, old versions can only really serve as historical markers, but are dead weight otherwise.