News for hackers. Stuff that matters.
Re:Improve your Git commits using patch mode by maaku on Sunday November 11, 2012 @02:18PM (#4770293)
Not necessarily. Use patch mode (or a tool like GitX that does the same job), commit, then stash and run your tests. If it's broken, amend your commit, rinse and repeat. Then push your changes or pop the stash and continue development.
Re:Improve your Git commits using patch mode by comex on Sunday November 11, 2012 @02:20PM (#4770298)
If you're going to stash anyway, sounds better to use stash -p and run the tests before committing.
Re:Improve your Git commits using patch mode by maaku on Sunday November 11, 2012 @02:22PM (#4770307)
Or that ;) I just wish my git-GUI of choice (GitX) supported that mode...
Re:Improve your Git commits using patch mode by masklinn on Sunday November 11, 2012 @03:05PM (#4770422)
I'm pretty sure I specified

> without stashing everything else

and noted that if you're going to stash the rest either way you could just as well use `stash -p` in the first place.

Re:Improve your Git commits using patch mode by emillon on Sunday November 11, 2012 @04:04PM (#4770587)
I am not sure why you insist on not stashing the rest of your working directory ? This is a nice and non-permanent solution.

There's a difference between `stash -p` and `add -p + stash`, though. If you want to split your changes into more than two commits, you have to use add/commit/add/commit because stash will just make a commit with "what's left" (it's subtractive operation).

Re:Improve your Git commits using patch mode by masklinn on Monday November 12, 2012 @03:12AM (#4772012)
Because it's an annoying extraneous command and I already know about this work-around si I don't need to learn about it.
Re:Improve your Git commits using patch mode by maaku on Sunday November 11, 2012 @09:37PM (#4771361)
Why purposefully avoid a tool designed for the job?