CODEWITHSUNDEEP
version-control
Adrian Jandl
Adrian Jandl

Reputation: 3015

Versioning for solo projects

I have been searching both google and other SO questions but none really describe my situation. I often create a copy of a project when I have a major feature working, so that I don't destroy it when I keep coding. Currently I am just copying the project in eclipse and renaming it to something like "MyProject2.0". This leaves my workspace VERY cluttered though.

workspace

Those are not huge upgrades, for normal versioning this is x.0.z, x.1.z, x.2.z at best. Should I just use Git or something similar? I am looking for a way to keep the old code(easily at hand) but also not clutter up my workspace like this.

Upvotes: 2

Views: 123

Answers (2)

Ahmed Masud
Ahmed Masud

Reputation: 22412

Any version control system will help. I've used rcs, cvs, svn and git along the way, any of them will do the trick for you. Choosing a revision control system, especially if you are a soloist is personal choice. You may want to consider git, as it is quite a good tool for what you are describing. GIT is well described on the git site with practical examples. Using it will surely get rid of your clutter. You should specifically read up on the git workflow that describes how to work with branches in a git controlled project. Also look at "stashing" in git, you'll see what I mean about git being nice for solo projects.

Upvotes: 1

Joey
Joey

Reputation: 354864

Yes, you definitely should. Use Subversion, Git, Mercurial, CVS ... whatever you feel fine working with. Even for solo projects version control software is a huge help in my experience.

Upvotes: 2

Related Questions