Following on from the first post a couple of months back I wanted to add a few more advanced workflows to my “how to git” series. In the previous article I talked about git from the perspective of a single developer executing simple changes to a repo and wanting to record that change at github.com. In this article I want to discuss multiple committers on a single repository and the use of branches.

This is a short and hopefully useful blog post on adding network latency and packet loss to nodes for testing the effect of latency and packet loss in a small local test environment. The post assumes that you already have a set of nodes running in a test environment and focusses introducing simulated latencies and other network phenomena using the unix ‘tc’ tool.

For the uninitiated and even the experienced git has a whole raft of confusing commands. The purpose of this article is to provide you with just enough git to do what we need. The purposes of this example I will be using a very simple private repo I created on my personal github account called “test-branching”. The basic workflow involves cloning a repository from https://github.com and then making some additions, deletions and modifications on your local laptop before eventually…