batinkov/deployment — pull request #1 by vanbesien (2014-11-10 17:50:11+00:00)
Title: Plots titles and some path corrections

After hours of battle with git, which brought me plenty of interesting insights, I present you: the first pull request you (@batinkov) will ever receive.
This just contains some updates to the file that was already committed to "batinkov" before.

Currently "vanbesien/deployment" is a fork from "batinkov/deployment", which is a fork from "dmwm/deployment".
Somehow I made the horrible mistake of cloning from "dmwm/deployment" instead of "vanbesien/deployment" for my local folder that was intended to have my personal git version.
This resulted in a lot of confusion when the push of my local branch suddenly contained not only my commit, but also all the commits that exist in "dmwm/deployment", but not yet in "batinkov/deployment". Of course I also had merging problems when trying to push to "vanbesien/deployment", because that one already contained a different version of shift_timing_layout.py, while from the standpoint of "dmwm/deployment" it was new. Long story short, it took some time to figure it all out, but is was quite insteresting. Now I have it all in the state that I want.

Each time you update your repo with "dmwm/deployment", I'll have to update my repo with yours. I don't think that this will ever pose any problems.
But if I update my repo directly with "dmwm/deployment" and "batinkov/deployment" is a few commits behind, then I'll be in trouble when I try to create a pull request.