VCS choices (Version Control Systems)

I recently bit the bullet and modernized myself...I'm all-in on using 'git' as my preferred 'version control system'.
Git explanation (wikipedia)
I chose 'git' because of 'github' (github.com), where I continue to find tons of open-sourced projects that are proving to be of immense help to me.
Wikipedia info for VCS is cataloged under the term 'Revision Control'. Here, they describe all the various choices available these days.
Revision Control explanation (wikipedia)

Some not-so-gory Git usage details

Since I'm now using Google's Android Studio for developing some code for Android, I've noticed that its support for various VCS choices are all neatly bunched under a common menu-choice labeled 'VCS'.

The first step in getting a given Android Studio project under source-code control is to choose the option 'Enable version control integration' while your project is open. They will then prompt you to choose which VCS you want to use for this project...[e.g 'Mercurial', 'Git', 'Subversion', etc] and finally finishes by creating a local 'repository' in which to store the various revisions of your coding files. (That option of course 'greys out' once you choose one. One small confusion is that the wording of the greyed-out choice changes somewhat, from the earlier phrasing before you execute it.)

From within Android Studio, I haven't yet found any way to reverse (undo) the decision to enable revision-control for a project, tho I suspect with some external git cmd-line hackery, there's a way to accomplish that.

Hmm...for my Slims_Sched proj, I chose to create a laptop-wide directory location ('Local_Git_Repo'), whereas later, for my newer 'Whats_Playing' proj, I forgot, so it defaulted and chose to create a proj-specific local git-repository inside that project's tree. (Yikes...not what I really intended. That will prolly confuse me later, so I mention this here to remind myself.)

TBD: I now need to go re-learn some cmd-line based git cmds, so I can inspect these local repos to see where I stand. :)

As I develop, I then periodically 'check-in' the changed files to the local repository. (You can do that either while inside the Android Studio IDE, or externally via the 'git' command-line.) I've learned to do check-ins from the IDE... under that same 'VCS' menu-item, I've been using the option 'Commit changes...', and it's smart enough to find my changed files and check-in anything I've updated, rather than requiring me to first do a 'check-out'. (I'm thinking this is 'safe' in my case, as no one else will ever use my 'local' repositories, since they're private to my laptop.)