3 ms·
That's a very good point. For the MantisBT project, we were interested in moving from SVN (after our initial move away from CVS) to a DVCS, and Git's excellent
by nuclear_eclipse 18y ago
That's a very good point. For the MantisBT project, we were interested in moving from SVN (after our initial move away from CVS) to a DVCS, and Git's excellent `git-svn` layer allowed us to experiment with using Git while still working on a day-to-day basis within our central SVN repository. It was an extremely useful method of evaluating a new source control tool, with reliable usage in pulling from and committing directly to the underlying SVN repository.
- nostrademons 18y agoIt's also really nice that git can often coexist with an existing VCS in the same working directory structure, and then you just delete the .git directory when you're done. I started using git this way - I had a svn project that I had to go offline with for about a week, so I setup a git repository so I wouldn't lose my work, and then just checked the final state in and deleted the .git directory afterwards. And I currently have to use Perforce at work, but I'll frequently setup a quick git repository to checkpoint large changelists while I'm working on them.