221–224 of 224 posts
Earlier quoted context omitted.
> After years of using git I got back to svn You get the best of both worlds--a sane set of commands and a distributed version control system--by using Mercurial [1]. Checking Status: SVN: svn status Mercurial: hg status Adding Files: SVN: svn add Mercurial: hg add Committing Changes: SVN: svn commit -m "Commit message" (commits changes directly to the central repository) Mercurial: hg commit -m "Commit message" (com…
And partial checkout?
VS Code is free, cross-platform, many people already use it, and has a very good GUI interface for git. It can easily do all the common workflows. I mainly use the CLI but if I already have a project open in VS Code I'll just do it in the GUI because it's actually faster in many cases and sometimes a bit more intuitive.
But then you have to use VSCode, and that's never a good thing.
After years of using git I got back to svn. Svn has one great feature, you can checkout (clone) repo partially. This way I can keep all my experiments in a single remote repo and easily pull any part of any project locally wherever I want. I don't really care about branching in svn. If I want to try variants of some code I still use git with multiple branches. I'm not sure what I would prefer for a team project. I'm…