# Summary of NanoEngineer Repository Migration Discussions

• Developers were working on converting the NanoEngineer-1 codebase from SVN to Git, achieving remarkable performance improvements with clone times reduced from approximately 14 hours to just 67 seconds, making the repository significantly more accessible to developers.

• The migration revealed poor repository management practices in the original SVN structure, including non-standard branch organization where branches existed in subdirectories rather than directly under the branches directory.

• Multiple conversion tools were tested, including git-svn, svn2git, and svn-all-fast-export, with the latter showing the most promise for handling the complex subdirectory structure and preserving the repository's history.

• The team encountered namespace conflicts where both tags and branches shared identical names (like "cad" and "sim"), complicating the conversion process and requiring manual intervention to properly convert SVN tags to Git's distinct tagging system.

• Many branches in the original SVN repository appeared to be abandoned immediately after creation with the cryptic commit message "Moved remotely," suggesting poor version control practices possibly exacerbated by developers using Windows with TortoiseSVN.

• A brief side discussion mentioned a TeleXLR8 event featuring Suzanne Gildert discussing hardware approaches to AI, where she argued against ASIC CPUs and advocated for investment in alternative computing paradigms beyond GPUs and FPGAs.