This is the first time I have encountered a problem that I couldn't fix. It simply refused to push changes. Maddening.

Thank heavens for git diff and git apply.

git apply editsfromborkedlocalrepo.diff
git commit -a
git push

And I'm back in business. No damned idea what was wrong with the initial local repo but I don't have time to play detective.

Cloned repo all over again. Made meaningless change. Pushed back successfully. Cloned yet again to make sure it indeed record change.

Now copy over 200 changed files to the freshly checked out repo to commit and push.

I have no clue what is wrong with the repo copy I was working on.

git not allowing me to push my changes to the remote.
About to go ballistic.

So strange finding myself in a position where 16GB of RAM isn't enough. Since the motherboard can't be expanded beyond that, it's time for an upgrade.

Twitter be a dumpster fire today.

Cars washed. Long circuitous journey with sidekick taken. Setting gvim up on the RHEL7 VM to my liking.

Meh. I'm going back outside. It's gorgeous out there. The ones and zeros can wait until evening.

@kdfrawg I've never met a software packaging system I couldn't heap scorn upon.

@kdfrawg Trading the arcane for the baroque is never a good decision.