While we appreciate comments from our users, please follow our posting guidelines. Have you tried the Cyotek Forums for support from Cyotek and the community?
Styling with Markdown is supported
03 January 2020 Reply
I made the change from SVN to Git a few years back, and I found the BFG repo cleaner to be a god-send. In the SVN days we just carelessly stored binaries and the like with the Git code, and I wanted to strip all of that out before the first commit. That utility was frighteningly easy to use and "just worked".
04 January 2020 Reply
Many thanks for taking the time to comment. I'll take a look at the BFG cleaner you mentioned although I think I'm fairly safe as I tend not to make a habit of chucking anything into SVN and with the exceptions of a few third party libraries from pre-NuGet days there are no binaries to be found.
I haven't decided yet if I'm going to convert my SVN repositories into a mono Git repo as the fashion these days is to have smaller repos, and I do have some cross pollution of projects, often in regards to shared resources - I don't like having a million copies of file-new.png for example and I do share the odd source file, e.g. PetaJson.cs.
I mainly find using Git makes me commit in a more responsible fashion. With SVN I make a million changes then commit them. With GitHub Desktop open on one monitor showing me the pending changes I tend to be much more methodical, making single changes, committing them and moving to the next. And if I do get over zealous and make multiple changes to a single file, Git (or GitHub Desktop) make it utterly trivial to commit those changes independently. I also feel that the branch and PR scenario is going to make more risky changes better than SVN.
Actually as I type out this comment I realise that I do need to migrate the whole thing to a mono repository, otherwise it'll never get done. I can always break things out later as required.
Again, thank you for taking the time to comment.