The SSH host key has changed on 8 April, 2022 to this one: SHA256:573uTBSeh74kvOo0HJXi5ijdzRm8me27suzNEDlGyrQ
Fork 0
Online Git Reference Forked from
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

113 lines
4.0 KiB

layout: reference
<div class="box">
<h2>Introduction to the Git Reference</h2>
<div class="block">
This is the Git reference site. This is meant to be a quick
reference for learning and remembering the most important and
commonly used Git commands. The commands are organized into
sections of the type of operation you may be trying to do, and
will present the common options and commands needed to accomplish
these common tasks.
Each section will link to the next section, so it can be used
as a tutorial. Every page will also link to more in-depth
11 years ago
Git documentation such as the official manual pages and relevant
sections in the <a href="">Pro Git book</a>,
so you can learn more about any of
the commands. First, we'll start with thinking about source code
management like Git does.
<div class="box">
<h2>How to Think Like Git</h2>
<div class="block">
The first thing that is important to understand about Git is
that it thinks about version control very differently than
Subversion or Perforce or whatever SCM you may be used to. It
is often easier to learn Git by trying to forget your assumptions
about how version control works and try to think about it in the
Git way.
Let's start from scratch. Assume you are designing a new source
12 years ago
code management system. How did you do basic version control before
you used a tool for it? Chances are that you simply copied your
project directory to save what it looked like at that point.
<pre> $ cp -R project project.bak </pre>
That way, you can easily revert files that get messed up later, or
see what you have changed by comparing what the project looks like
now to what it looked like when you copied it.
If you are really paranoid, you may do this often, maybe putting the
date in the name of the backup:
<pre> $ cp -R project project.2010-06-01.bak </pre>
In that case, you may have a bunch of snapshots of your project that
you can compare and inspect from. You can even use this model to
fairly effectively share changes with someone. If you zip up your
project at a known state and put it on your website, other developers
can download that, change it and send you a patch pretty easily.
$ wget
$ unzip
$ cp -R project.2010-06-01 project-my-copy
$ cd project-my-copy
$ (change something)
$ diff project-my-copy project.2010-06-01 > change.patch
$ (email change.patch)</pre>
Now the original developer can apply that patch to their copy of the
project and they have your changes. This is how many open source
projects have been collaborated on for several years.
This actually works fairly well, so let's say we want to write a tool
to make this basic process faster and easier. Instead of writing a tool
that versions each file individually, like Subversion, we would probably
write one that makes it easier to store snapshots of our project without
having to copy the whole directory each time.
This is essentially what Git is. You tell Git you want to save a snapshot
of your project with the <code>git commit</code> command and it basically
records a manifest of what all of the files in your project look like at
that point. Then most of the commands work with those manifests to see
how they differ or pull content out of them, etc.
<center><img src="./images/snapshots.png"/></center>
If you think about Git
as a tool for storing and comparing and merging snapshots of your project,
it may be easier to understand what is going on and how to do things
<p><a class="page-button next-page" href="/creating">On to Getting and Creating Projects &#187;</a></p>