News for hackers. Stuff that matters.
Re:Why is git pull considered harmful? (2013) by gbog on Wednesday March 12, 2014 @10:45PM (#7389794)
Not sure.

Do you think Da Vinci sat at his table and thought "let's invent the helicopter" (with a nice unique memorable name for his work in progress)?

I would rather imagine Da Vinci being supposed to draw some boring architectural work or even writing against his will to his great-grant aunt. And then a paper fell off his table, spinning away. And then I imagine Da Vinci drawing a spinning paper on the margins, and adding equations, schemas, and getting deeply inside this new project, which becomes clearer in his mind as he works on it, without ever having a name.

This is exactly why I hate deciding a branch name before some tasks and I love `git add -p` which allow me to add a bucnh of unrelated things in the work tree and extract the juice later.

Re:Why is git pull considered harmful? (2013) by yock on Thursday March 13, 2014 @10:54AM (#7392158)
Here, $10 well spent. Watch and be enlightened.

http://pragprog.com/screencasts/v-jwsceasy/source-control-ma...

Re:Why is git pull considered harmful? (2013) by yock on Thursday March 13, 2014 @10:53AM (#7392149)
With git you can experiment to your hearts content. Then, once you decide you have something ready to go, create the branch and commit to it. You don't have to create the branch first.
Re:Why is git pull considered harmful? (2013) by dllthomas on Thursday March 13, 2014 @10:54AM (#7392161)
Or even create some branches called "experiment1", "experiment2", &c, until you figure out what it should be called.