HNHacker News
TopNewBestAskShowJobs

drizzo4shizzo

8 karma · joined October 4, 2012

submissionscomments
drizzo4shizzo··on Show HN: we like to work from coffee shops, so we made this
The velcro yes, but please, please no on the other idea.

Next time I can't find a table to eat lunch at Panera the guy entrenched at a 4-person table for hours with a laptop and single coffee cup is going to try and make me read ADS? This... would be unwise.

drizzo4shizzo··on Proposition HN: I will pay $8000 for you to build your side-project/MVP
wow has NOBODY considered the idea that this guy is just harvesting your ideas?

who knows how sincere the offer is.

phishing 101

drizzo4shizzo··on Kickstarter backers ready class action lawsuit against Code Hero dev
Release the code. The backers are the code heroes. They can fix it. That's the game.
drizzo4shizzo··on Big News From Mars? Rover Scientists Mum For Now
Found: one discarded fixed-gear warp drive. Damn. Hipster. Jedis.
drizzo4shizzo··on Apple told to rewrite "Samsung didn't copy", post on front page until Dec 14th
They'll probably put Ironic Hipster quotes around "copy"
drizzo4shizzo··on Linus on keeping a clean git history (2009)
If you have commits in your local branch and you are doing a pull without --rebase you can get merge commits, but I believe those messages should be generated for you(?). I almost always choose rebase over merge so there are no merge commits, all my merges are fast forward. Check your workflow.

Regarding your second question, you want "git add -a". Git gives you the ability to commit "some of what I've changed here", even within files (see git add -i). This facilitates clean commit history by letting you control exactly what is in each commit (even if you changed other files).

And even once you've made your commits to your private branch of course you can continue to change the order of them or combine them with interactive rebase... until you push...