-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathvocab.html
99 lines (90 loc) · 3.51 KB
/
vocab.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>RIT CS Git Tutorial | Vocabulary</title>
<link rel="SHORTCUT ICON" href="Media/CSC_logo.ico">
<link rel="stylesheet" type="text/css" href="custom.css">
</head>
<body>
<!-- header -->
<div id="topbar">
<div class="barbutton">
<img height="40" src="Media/CSC_logo.PNG"/>
</div>
<div class="barbutton">
<a href="index.html">Home</a>
</div>
<div class="barbutton">
<a href="vocab.html">Vocab</a>
</div>
<div class="barbutton">
<a href="setup.html">Setup</a>
</div>
<div class="barbutton">
<a href="committing.html">Committing</a>
</div>
<div class="barbutton">
<a href="eclipse_setup.html">Eclipse and Git</a>
</div>
<div class="barbutton">
<a href="general.html">FAQ</a>
</div>
<div class="barbutton">
<img height="40" src="Media/git.png"/>
</div>
</div>
<!-- end header -->
<h1>Vocabulary and Basic Concepts</h1>
<!-- ====================================================================== -->
<h2>What is version control?</h2>
<div>
<p>Version control is used to keep track of the changes made
on a set of files over time
(commonly known as "revisions" or "commits").
This is useful for recovering from accidentally deleted or broken code
and for collaborative coding in a team.
Git is a popular modern version control system that is used
by many free and open source software projects,
as well as numerous tech. companies.
</p>
</div>
<!-- ====================================================================== -->
<h2>An overview of the Git repository</h2>
<div>
<p>Each Git repository consists of a <code>.git</code> folder
and the working directory.
The <code>.git</code> folder contains a representation of
the version history and
is usually located inside the working directory.
The working directory contains the currently "checked-out" commit;
a staging area (also called the "index") where you collect changes
in preparation for creating a commit;
and a tree of commits, each of which represents
a set of related changes to the project.
</p>
<p>Each "change" (or commit) consists of a user-entered message
describing the changes that were made,
a representation of the changes themselves,
and a pointer to the previous commit(s).
In this way, Git creates a tree of commits that shows
the evolution of a project over time.
</p>
<p>
<img src="Media/working_staging_repositorying.png" alt="The working directory, staging area, and tree of commits"/><br/>
The working directory, staging area, and tree of commits.<br/>
(Image credit: <a href="http://git-scm.com/book/en/Getting-Started-Git-Basics" target="_blank">Pro Git</a> by Scott Chacon)
</p>
</div>
<!-- ====================================================================== -->
<h2>How is Git different than other version control systems?</h2>
<div>
<p>Git is a distributed version control system,
which means that every developer's machine contains a complete copy of the repository;
thus, the entire history of the codebase is always stored locally.
This is in contrast to many older such sytems that only stored this information on one centralized server.
</p>
</div>
<!-- ====================================================================== -->
</body>
</html>