What I’ve done in the past is to have a default config file which is checked in to source control. Then, each developer has their own override config file which is excluded from source control. The app first loads the default, and then if the override file is present, loads that and uses any settings … Read more
Have you ever: Made a change to code, realised it was a mistake and wanted to revert back? Lost code or had a backup that was too old? Had to maintain multiple versions of a product? Wanted to see the difference between two (or more) versions of your code? Wanted to prove that a particular … Read more
The SHA is just one representation of a version (albeit canonical). The git describe command offers others and does so quite well. For example, when I run git describe in my master branch of my Java memcached client source, I get this: 2.2-16-gc0cd61a That says two important things: There have been exactly 16 commits in … Read more
The main difference is that (as it was already said in other responses) CVS is (old) centralized version control system, while Git is distributed. But even if you use version control for single developer, on single machine (single account), there are a few differences between Git and CVS: Setting up repository. Git stores repository in … Read more