Re: `git stash pop` UX Problem
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Feb 25, 2014, 23:50 UTC
- Message-ID
- <20140225235015.GE250380@vauxhall.crustytoothpaste.net>
- In-Reply-To
- <vpqzjlf5q2z.fsf@anie.imag.fr>
On Tue, Feb 25, 2014 at 01:33:56PM +0100, Matthieu Moy wrote:
Show 10 quoted lines
> Holger Hellmuth <hellmuth@ira.uka.de> writes: > > Maybe status should display a stash count if that count is > 0, as > > this is part of the state of the repo. > > Maybe it would help some users, but not me for example. My main use of > "git stash" is a safe replacement for "git reset --hard": when I want to > discard changes, but keep them safe just in case. > > So, my stash count is almost always >0, and I don't want to hear about > it.
I concur with this. Sometimes the stashed changes are remnants of a small hack or a very brief start to an aborted project that I stashed when I needed to change branches. I figure that they might be useful in the future, but I don't care about them right now. I may pick them up, I may not, but I certainly don't want to be reminded of them constantly.
-- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187