I feel like the forum mods should split this into two discussions - one as a "how to" and another as a "SVN vs. git" discussion.
dont worry much. the thread runs out.I feel like the forum mods should split this into two discussions - one as a "how to" and another as a "SVN vs. git" discussion.
and another as a "SVN vs. git".
... apparently urged by xCode ?.... I was urged to setup a Git-repository on my server for my most active development projects, one of which is visible on GitHub as well (https://github.com/cyclaero/ContentCGI).....
Yes, Subversion support has been discontinued in Xcode 10. Then I migrated my most active development projects to Git. Later I found out, that I may have several Xcode versions on my development machine side-by-side, and for the time being I leave my other projects in Subversion.... apparently urged by xCode ?
Yes, Subversion support has been discontinued in Xcode 10. Then I migrated my most active development projects to Git. Later I found out, that I may have several Xcode versions on my development machine side-by-side, and for the time being I leave my other projects in Subversion.
...
I wished that svn stayed in xCode , ....
I would like to respectfully disagree. I used Perforce (a.k.a. P4) for about three years, about 10 years ago. It was excellent. The most important part was that it was powerful (really good merging engine, for getting stuff merged up and down branches), while being easy to use. For really simple workflows (non-branched development with a central repository and only 2-3 active developers), it was as easy to use as CVS, and we had a cheat cheat that translates CVS commands to P4 commands.Other than avoiding Perforce, I don't think I really have a preference on any VCS. They all have pros and cons (Perforce only has cons .
I used Perforce (a.k.a. P4) for about three years, about 10 years ago. It was excellent.