> Sometimes, something needs fixing ASAP, and you have 260 build-breaking lines an hour away from being commit-worthy If you have 260 lines of code you should

> Sometimes, something needs fixing ASAP, and you have 260 build-breaking lines an hour away from being commit-worthy If you have 260 lines of code you should have committed it already. I disagree with the article. stash is the wrong solution for a substantial set of changes tied to a particular branch -- instead you should use a temporary branch, and relax about using git reset to rework it later. > clone a new copy of the repository The thought shouldn't even be entering your mind.