This section will go through the most basic parts of git. More in-depth tutorials and information can be found on the official git webpage. I liked this very cute intro as well.

Cloning a repository

The first thing to do in this course is to clone the course repository where all the notes, homework and labs are. First cd into the directory where you want the place the repository then:

bash-3.2$ git clone
Cloning into 'math_557_finite_element_analysis'...
remote: Counting objects: 14, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 14 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (14/14), done.
Checking connectivity... done.

Listing the contents of the directory you will see something like this (there might be more stuff added by the time you read this)

bash-3.2$ ls math_557_finite_element_analysis/
README.rst      notes           slides

We can now change directory into the repository and fetch new contributions from the origin and merge them to your master branch. The origin is the remote repository at bitbucket and the master is the main branch in your local repository.

bash-3.2$ cd math_557_finite_element_analysis/
bash-3.2$ git fetch origin
bash-3.2$ git merge origin/master
Already up-to-date.

Of course, as we did not change anything git told us we are already up-to-date.

The basic work-flow

Suppose I now want to make some changes to the file GIT.rst (containing the text that eventually gets typeset to html by Sphinx) then I can use an editor like emacs to open and edit the file bash-3.2$ emacs GIT.rst &. When done editing I can ask git for a report of the status of my local repository

bash-3.2$ git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#       modified:   GIT.rst
no changes added to commit (use "git add" and/or "git commit -a")

The message from git tells me that I am on the master branch and that I have made changes to the file GIT.rst which is under version control. To commit the changes we first add them to the staging area and then commit them together with an informative message:

bash-3.2$ git add GIT.rst
bash-3.2$ git commit -m "Added a heading to the GIT.rst file"
[master a255475] Added a heading to the GIT.rst file
 1 files changed, 2 insertions(+), 1 deletions(-)

Now we can take a look at the status again:

bash-3.2$ git status
# On branch master
nothing to commit (working directory clean)

We can also take a look at the history of the previous commits

bash-3.2$ git log
commit 2b40eb75a1b03192c84b398564ee002e026b8f81
Author: Daniel Appelo <>
Date:   Tue Dec 30 14:55:07 2014 -0700

    First commit

The long hex-string 2b40eb75a1b03192c84b398564ee002e026b8f81 is the name of the commit and is computed by SHA-1 hash. This name is what allows you to get back to older versions of the code.

If we are happy with the commit we just did we can push it to the remote repository at

bash-3.2$ git push
Password for '':
Counting objects: 4, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 668 bytes | 0 bytes/s, done.
Total 4 (delta 2), reused 0 (delta 0)
   2b40eb7..c11f86b  master -> master

Pushing your commits to the remote server concludes the basic work cycle. Of course you can do multiple local commits before you push. In Homework 1 you will learn more about how to initialize and work with git.