Version Control Tools: SVN
Someone once said: The past cannot be changed, forgotten, edited, or erased. It can only be accepted . But then programming came into being and it stated that "you can change your past, but only the code past". Meaning; what you have coded earlier you can change, edit and improve it. And for that you need to have something like revision history, from where you can get the idea of what you have done (coded) in the past. Questioning.. So how would you keep the history of your code? Would you make several copies after doing each and every change? Or will you opt for "control/command + z"? Obviously you don't go for such an inefficient way of controlling the version/history of your code while working on some large project. Answering... So here comes "version control systems". These systems/softwares are specially designed to help you in controlling the version of your project codes. They also enable you to share your code and collaborate...