Re: `git stash pop` UX Problem

3 messages, 3 authors, 2016-06-15 · open the first message on its own page

Re: `git stash pop` UX Problem

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:59:59

Holger Hellmuth [off-list ref] writes:
Am 24.02.2014 17:21, schrieb Matthieu Moy:
quoted
$ git add foo.txt
$ git status
On branch master
Changes to be committed:
   (use "git reset HEAD <file>..." to unstage)

         modified:   foo.txt
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.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: `git stash pop` UX Problem

From: Omar Othman <hidden>
Date: 2016-06-15 22:59:59

Well, it's called `git stash` and not `git trash`... :-D

That's your own usage of it, but its main usage is different.

This is not a solution, but it's better than nothing and I second it.

On 25-02-14 13:33, Matthieu Moy wrote:
Holger Hellmuth [off-list ref] writes:
quoted
Am 24.02.2014 17:21, schrieb Matthieu Moy:
quoted
$ git add foo.txt
$ git status
On branch master
Changes to be committed:
    (use "git reset HEAD <file>..." to unstage)

          modified:   foo.txt
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.

Re: `git stash pop` UX Problem

From: brian m. carlson <hidden>
Date: 2016-06-15 23:00:00

On Tue, Feb 25, 2014 at 01:33:56PM +0100, Matthieu Moy wrote:
Holger Hellmuth [off-list ref] writes:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help