The document discusses version control systems (VCS) and their importance in software development, emphasizing their role in enabling collaboration among programmers. It outlines the differences between centralized and distributed VCS, detailing their workflows and advantages. Popular version control tools like Git and Mercurial are introduced, along with basic commands for using Git effectively.

1. VCS
Three letters that can change your life

2. WHY DO I TALK ABOUT THIS?

3. MEET MAIN CHARACTERS
This is a story with a few characters. Let meet
them!

4. Cthulhu The Cute

5. Twilight The Gentoo Pony

6. Shadow The Gamer

7. ONCE UPON A TIME IN R'LYEH
PROGRAMMING UNIVERSITY...

8. Shadow played games the whole semester. At
the end of the semester he had to do a lot of
tasks but he did not know how.

9. So he asked Twilight for help

10. And then the terrible thing happened

12. CUTE CTHULHU'S WISE WORDS:

13. SO WHY DO I TALK ABOUT
THIS?

14. BECAUSE...
Sharing source code as attachments in social
networks is like using stone instruments
nowadays

15. BECAUSE...
Version control systems simplify software
development
Especially when several people work on the
same code together

16. BECAUSE...
It is vital to programmer to know how to use
version control systems

17. BORING PART

18. WHAT IS VERSION CONTROL
SYSTEM?
“ Version control is a system that
records changes to a file or set of
files over time so that you can
recall specific versions later.”

19. GOALS OF VCS
Allow developers to work simultaneously.
Do not overwrite each other’s changes.
Maintain history of every version of
everything.

20. VCS CLASSIFICATION
Centralized version control systems (CVCS)
Distributed version control systems (DVCS)

21. CENTRALIZED VCS
There is a single “central” copy of your project
somewhere, and programmers commit their
changes to this central copy.

22. CVCS WORKFLOW
1. Pull down any changes other people have
made from the central server.
2. Make your changes, and make sure they
work properly.
3. Commit your changes to the central server,
so other programmers can see them.

23. DISTRIBUTED VCS
Do not necessarily rely on a central server to
store all the versions of a project’s files.
Every developer clones a copy of a repository
and has the full history of the project on their
own hard drive

24. ADVANTAGES OVER CVCS
Faster
Nobody sees unfinished work
Less dependent on Internet

25. VERSION CONTROL SYSTEMS
About 46 VCS exist now ( )https://goo.gl/imTGhs

26. THE MOST POPULAR VCS
Subversion
Git
Mercurial

27. INTERESTING PART

28. HELLO, GIT!

29. INITIALIZE AN EMPTY
REPOSITORY
git init

30. ADD FILES
git add

31. COMMIT CHANGES
git commit

32. WHAT IS YOUR STATUS?
git status

33. LOCAL HISTORY
git log

35. BRANCHES
git branch

36. SWITCH WORKING TREE
git checkout

37. GET IT TOGETHER
git merge

38. PUT ONE ONTO ANOTHER
git rebase

39. WORKING IN TEAM

40. REMOTES
git remote add <name> <address>

41. SEND COMMITS TO REMOTE
git push <remote> <branch>

42. UPDATE FROM REMOTE
git fetch <remote>
git pull <remote>

43. WHAT TO READ NEXT?

44. GIT
Git documentation
Atlassian tutorials about git
Git in 15 minutes
Git tree planting
What to do if you messed your Git repository

45. MERCURIAL
Mercurial official website
Great Mercurial tutorial
Comparison of Git and Mercurial
Working qwith bookmarks

46. Presentation by Oleksandr Kovalchuk

47. THE END
ANY QUESTIONS?