Myself in 1991, with a bit of 92 and 93. Soundtrack from 1994.
Hamilton, Burlington, Oakville, Guelph, Kenogami (Timiskaming).
Category: Uncategorized
L’ Ordre secret
Tous les frères ont un esprit identique.
Sa force réside dans son ensemble.
La doctrine du sacrifice personnel.
Aimer son peuple d’un amour véritable,
l’aimer objectivement sans intérêt personnel,
sans aveuglement, est une voie raisonnée et pratique.
Nous travaillons pour la cause,
pas pour les éloges.
Nous cherchons une action efficace.
La fraternité chez nous est une force unifiante et non assimilatrice.
Elle ne tue pas la personnalité mais seulement l’individualisme.
Cherche le bien général.
Git Squash at the Command Line with a Bash Script
Useful if the commits on your branch are sloppy, and you want to clean them up, and you don’t mind that your new commits will be file based instead of time based.
What does that mean exactly? Let’s say you worked two days on 3 files. (One of the files was a class, another a config, and the third a unit test.) Over the course of two days you made 13 commits. Sometimes a commit was to one file, sometimes a commit was to both, sometimes all three… 13 times! (Sloppy! You should be ashamed.) After running the script below you will lose 13 commits but can restage and create either a single commit message, or up to 3 new commit messages: One for each file. (Clean! Dick Grune approved.)
Useful if you’re too lazy to use rebase with fixup. Instead, just run one cheap and barely good enough bash script and you’re done. So lazy in fact you’re scrolling through all these words not even reading them, get to the script already.
Useful in scenarios where GitHub’s Squash & Merge interface is unavailable.
Prerequisites before running the script below, where feature/foo is your branch:
- The script is saved somewhere in your path.
- You are working on branch feature/foo. You want to create a single squashed commit, or restage in batches, up to as many commits as you have files.
- You have merged “destination” into feature/foo and resolved conflicts.
- You are the author of all the commits on feature/foo (Or want to be the author? You will be rewriting…)
- You are currently on feature/foo.
#!/bin/bash set -e destination='master' branch=$(git rev-parse --abbrev-ref HEAD) git checkout ${destination} git pull git checkout ${branch} git checkout -b ${branch}-backup git checkout ${destination} git branch -D ${branch} git checkout -b ${branch} git merge --squash ${branch}-backup _done=" Everything seems fine. Next steps: git status git commit # Or re-stage and do multiple commits git push --force-with-lease --set-upstream origin ${branch} To undo: git reset HEAD . git checkout -- . git checkout ${destination} git branch -d ${branch} # If branch exists on GiHub: git branch -D ${branch}-backup git fetch git checkout ${branch} # Else: git branch -m ${branch}-backup ${branch} " echo "$_done"
After running this script your files will be staged. You can either rewrite a nice single commit message for all the files, restage and commit in batches, or undo.
Inspired by this Gist.
I just want a phone. Is that too much to ask?
Subtitle: How to disable Google Now Cards (that keep annoying you) when you swipe left (right? up? argh, fuck this shit!)
I own an Android phone.
In an effort to get rid of a feature that came with updates I’ve been going through dozens and dozens of settings. Unsuccessful, at wit’s end, writing angry loner feedback to Google support (also known as /dev/null) begging for them to make it easy for users to opt out of what I consider intrusive garbage when it turns out I can simply replace the launcher.
KISS is a programming principle that stands for “Keep it simple, stupid!” The KISS Launcher code is GPL and available on GitHub. The Kiss Launcher app is available for free on Google Play.
#dadphone
Machine Ethics and Emerging Technologies
Keep your eyes off the fabulous hat because this talk is great.