Version Control

Question 1

Types of Version Control Systems

Answer 1

Local
Centralized
Distributed

Question 2

Local database keeps
track of file versions

Answer 2

Local VCS

Question 3

RCS (Revision Control System) is an example of a

Answer 3

Local VCS

Question 4

VC systems either keep:

Answer 4

● actual copies of file versions; or
● patch sets, which are the set of additions /subtractions to a file.

Question 5

A single server contains the file versions

Answer 5

Centralized VCS

Question 6

Clients check out
individual files/folders
from the central server

Answer 6

Centralized VCS

Question 7

Advantages of Centralized VCS

Answer 7

Collaboration with others is possible
Easy to administer file permissions

Question 8

Disadvantage of Centralized VCS

Answer 8

✘ Single point of failure

Question 9

Concurrent Versions System (CVS), Subversion and Perforce is an example of what kind VCS

Answer 9

Centralized VCS

Question 10

In this type of VCS, the Machines fully mirror the repository, including the
history of changes

Answer 10

Distributed VCS

Question 11

Peer-to-peer approach

Answer 11

Distributed VCS

Question 12

Each peer is a valid
repository

Answer 12

Distributed VCS

Question 13

TRUE or FALSE:

Distributed VCS addresses the single point failure issue of Centralized VCS

Answer 13

TRUE. Since in Distributed VCS, multiple users can have a copy of the repository

Question 14

Disadvantage of Distributed VCS

Answer 14

✘ Large repositories may be impractical to mirror (either due to large files, or very long histories)

Question 15

Give examples of Distributed VCS

Answer 15

Git, Mercurial, Bazaar, Darcs

Question 16

Advantages of VCS

Answer 16

Backup & Restore
Short-term / Long-term undo
Synchronization
Track Changes
Track Ownership
Branching/Merging

Question 17

Save all your changes and jump to any
version at any time.

Answer 17

Backup & Restore

Question 18

No fear of experimental changes, whether short or long term.

Answer 18

Short-term / Long-term undo

Question 19

Stay up to date with teammates’ work.

Answer 19

Synchronization

Question 20

Track the development of each file, and
explain why the changes happened.

Answer 20

Track Changes

Question 21

Find out who made a particular change.

Answer 21

Track Ownership

Question 22

Make a copy of your code that you can modify in isolation. You can delete, or merge this copy back to the ‘main’ version.

Answer 22

Branching/Merging

Question 23

Where the files are stored

Answer 23

Repository

Question 24

Repositories can be ________ or _________

Answer 24

remote, local

Question 25

Local repos are also called the ________________

Answer 25

working copy

Question 26

a copy of another repository (all the files, and revision history)

Answer 26

Clone

Question 27

To record the changes in the VC history/log, a version or ‘checkpoint’ that you can go back to any time

Answer 27

Commit

Question 28

The latest commit in the repository

Answer 28

Head

Question 29

A copy of the code base

Answer 29

Branch

Question 30

TRUE or FALSE: Each branch can evolve separately from other branches

Answer 30

TRUE

Question 31

The stable code is usually found in a ______ branch (in Git this is called _________)

Answer 31

main, master

Question 32

Different branches can be merged together

Answer 32

Merge

Question 33

Conflicts must be _________

Answer 33

resolved

Question 34

When there are two or more conflicting changes to the same file

Answer 34

Conflict

Question 35

To get all the latest changes from the remote repo and put them in your local repo

Answer 35

Update/Sync

Question 36

A distributed version control system, Free and open-source software, Primarily a command line tool, Has 3rd party GUI and add-ons for IDEs

Answer 36

Git

Question 37

A website/service designed to function with Git (but not other VCS) Main function: Allows users to create git repositories on their server

Answer 37

GitHub

Question 38

Alternatives to GitHub

Answer 38

GitLabs, BitBucket