shared gitconfig

[Vladimir Panteleev]

On Tuesday, 8 January 2013 at 07:07:18 UTC, Andrei Alexandrescu 
wrote:
> This script is bad because it does not do any meaningful error 
> handling and offers no good explanation on how to proceed if 
> either step fails.

Indeed - I wanted to avoid using any syntax / commands that 
someone wouldn't use in daily git use.

> If you thought I had this kind of style in mind, I agree that 
> using such scripts is a terrible idea.

However, I can't think of any scenario where a command would fail 
half-way through the script and lead to undesirable consequences, 
assuming the git repository is not corrupted. The recovery 
instructions would still apply.

Therefore, just add "set -e" at the top for the peace of mind.