Skip to content
Snippets Groups Projects
Commit 624202bc authored by Dirk Sarpe's avatar Dirk Sarpe
Browse files

start block 0: why vcs

parent f5c39097
No related branches found
No related tags found
No related merge requests found
# Introduction to git - a powerful version control system
## Why would you want to use a VCS?
### 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 change broke or fixed a piece of code?
- Wanted to review the history of some code?
- Wanted to submit a change to someone else's code?
- Wanted to share your code, or let other people work on your code?
- Wanted to see how much work is being done, and where, when and by whom?
- Wanted to experiment with a new feature without interfering with working code?
In these cases, and no doubt others, a version control system should make your life easier.
To misquote a friend: A civilised tool for a civilised age.
by si618 at [https://stackoverflow.com/a/1408464](https://stackoverflow.com/a/1408464)
### Does this look familiar?
Picture with many draft versions.
Punchline: Not only for code.
### A VCS gives you a history of your project:
* dcad3f8 add table captions for fwb
* 92531e7 figure captions for fwb
* 5129bdd adapted figure to fig for fwb and minor
* fff1924 minor: fix reference name
* dda1e33 adapt abstract to numbered fwb summary
* d2f46d3 compare real TCI and our TCI
* 35787b1 some mean values we need to report
* 6af0b79 denser conclusion
img/draft_mess.png

98.3 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment