Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
15 views13 pages

Sujith 2

Uploaded by

reddysunny382
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as KEY, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views13 pages

Sujith 2

Uploaded by

reddysunny382
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as KEY, PDF, TXT or read online on Scribd
You are on page 1/ 13

HELLO

Source Code Management:


History & Overview

N.Sujith Reddy
22681A0580
Module Objectives

1 3
Different Types of VCS

History of Version
Control Systems
5
VCS:Git

2
Operation on VCS
4
Concurrent Version System
Brief History of Version Control
Systems
Brief History of Version Control
Systems
Basic Operations in a VCS
There are a set of basic operations performed in a VCS. These are as follows:
1. Create
2. Checkout
3. Commit and Update
4. Add, Edit and Delete
5. Rename and Move
6. Status, Diff and Revert
7. Log and Tag
8. Branch and Merge
9. Resolve and Lock
Examples of Version Control Systems
Concurrent Version System (CVS)

CVS stands for Concurrent Version System. It is a version control system


that has been developed in the public domain by many people beginning
in 1986. Currently, CVS is maintained by Cyclic Software.

CVS is an open-source software configuration management utility


designed to manage different versions of the same software project in a
specialized repository.

Using CVS, you can record the history of your source files (normally text
files, binary files are handled with some restrictions). Instead of save
every version of every file, CVS stores only the differences between the
versions.
Concurrent Version System (CVS)

Moreover, CVS allows you to isolate changes onto a separate line of


development, known as a branch. When you change files on a branch,
the changes do not appear on the main trunk. Later you can move the
changes from one branch to another branch (or the main trunk) by
merging.

CVS manages different versions of the module so that if a future


version encounters some defects, a past version can be referenced and
used.
Repository and Working Copy

The CVS repository stores a complete copy of all the files and directories
which are under version control. Normally, you never access any of the
files in the repository directly. Instead, you use CVS commands to get your
own copy of the files into a working directory, and then work on that copy.
CVS can access a repository by a variety of means. It might be on the local
computer, or it might be on a computer across the room or across the
world. Using CVS with a remote repository we talk about client/server
operation. Several protocols are supported to connect to the remote
repository, e.g. rsh, password authentication, GSSAPI, kerberos.
You can define several repositories if you have different development
groups that work on separate projects without sharing any code. All you
have to do is to specify the appropriate repository when you are starting
the session.
Git

Git is a version control system designed to manage the teamwork done on a


project. Git helps the contributors to track the changes in files or projects and
speed up the overall process.

Git is an Open Source Distributed Version Control System. It is designed for:

Speed

Simplicity

Fully Distributed

Excellent support for parallel development, support for hundreds of parallel


branches.
Advantages of Git
Thank
You….

You might also like