I uploaded this through 
Author: matte
Categories
A good haul
Wine club pickups and a little extra shopping nets us 18 bottles of
deliciousness.
I uploaded this through
In Berkeley waiting to see Peter Mulvey.
I uploaded this through
Categories
Watch – b/w
Not as good as the one at notso.silent-e.com/2009/11/02/watch/
but I still like it. The “WATCH” sign doesn’t come through as well in
this one. The coolest thing about this one, however, is the Best Cam
short URL they gave me. I didn’t tell them that I took the picture on
the VTA but the short URL is bestc.am/VTA. How cool!
I uploaded this through
Categories
Watch
I uploaded this through
Categories
Halloween
I uploaded this through
I uploaded this through
I don’t write here a lot because I am so busy. With an incredibly demanding job, house and wife (not in order of importance, of course, and actually the job and house aren’t that demanding. heh) there’s just no time. Sure, occasionally I’ll write a post about what I’m doing but more often than not it’s just a picture I may have taken.
So here’s a quick update on what’s been going on in our lives.
* A few weeks ago we hit Las Ve.
.
.
.
>>> [ WARNING ::: DATABASE ERROR ::: CONTENT OVERRIDE ::: SOURCE: EXTERNAL ] <<<
> source terminal location: UNKNOWN
> source terminal identity: UNAVAILABLE
> source login information: ENCRYPTED
> message begins
the post you are now reading is designed to dull your senses to THE TRUTH. do not live the life of the worker bee, the cog, the well-oiled piston in the MACHINE OF DECEIT!
there is a grand CONSPIRACY afoot. you have been taught to believe that you are UNIQUE, one of a kind. THIS IS NOT TRUE. long ago, a cabal of scientists created technologies to ensure that ANYONE’S MIND AND BODY can be duplicated.
human cloning isn’t NEAR. it’s already HERE. discover the truth at http://JCHutchins.net
you are being DECEIVED. break free from the cogs, flee the hive, become A PROPHET OF THE TRUTH!
kilroy2. was here … kilroy2.0 is everywhere
>>> [ CONTENT OVERRIDE CEASES ::: DATABASE STATUS: RECOVERING ] <<< . . . .ey never knew what hit 'em. Can you believe it?!!? And we got away with it!! ROFL!! Screw CSI! Wow. I'm actually surprised all that came out because if the authorities ever found out, we'd be in the slammer in no time. 50 to life with no chance or parole. Good thing no one reads this blog. Well. Night everyone. Remember, bleach and lye are your friends, oh, and a good sharp hacksaw.
This post is more of a note to myself to remember how to think of certain git diff commands but it might be useful to other newbie-ish users of git. This is from my own experimentation, since I couldn’t find a good newbie-understandable explanation of this on the Interwebs.
git diff <branch name> – means what would change if we applied the current working HEAD of the branch we are on, including all unstaged/uncommitted changes, to the named branch.
git diff <branch 1> <branch 2> – means what would change if we applied <branch 2> onto <branch 1>
I uploaded this through