Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • some very good points made, my problem with using VSS on its own, is the standard practice here is to commit when there is a "build". hence why i want to keep my "feature work/"experiments" in a git branch Commented Oct 23, 2014 at 12:33
  • 1
    You might as well just keep them in a different directory - if you don't have a remote repo, a local git is only going to give you history. You woudl be far better off helping them migrate to a different SCM - I'd recommend SVN as the step from VSS to git is HUGE, whereas VSS to SVN isn't nearly as daunting from a sysadmin or management PoV. In a couple of years you can then migrate them again to Fossil, or git if absolutely necessary. Commented Oct 23, 2014 at 13:00
  • local git gives me the ability to revert, bisect, jump between branches etc. All these things that i would struggle without now :p. I simply don't develop software without git anymore even at home, for personal projects that stay local. I agree I would be better off getting them to migrate the project, but that's unlikley, they did migrate to synergy a few years back but only for new projects, old projects like the one i am working on are in VSS. I can't really comment on whether they should replace synergy as I have not used it yet. Commented Oct 23, 2014 at 15:29
  • 1
    gbgbaanb, I disagree about the migration. Folks new to the industry learn git and how it works. Making folks switch source control twice within a couple of years is unproductive imho. I would even make the case that vss directly to git is suitable precisely because the gap is go big. Just learn the new thing, not something 'close' to it. I've also seen huge number of svn users get really confused when moving to git as the same words mean different things. For those folks I wish they'd never learned svn at all to avoid that confusion. imho and ymmv of course :) Commented Oct 29, 2014 at 11:51
  • 1
    @MichaelDurrant I sometimes wish I had never had SVN, but more because it got me hooked on a GUI! I spent the first few months with git searching for a GUI I liked. Now I find myself going straight to the VSS command line help :p Commented Nov 3, 2014 at 9:40