On June 11, 2017 1:07 PM liam Beguin wrote: >There is one thing I've noticed though. When using 'git stash pop', it shows the the number of stashes before dropping the commit and I'm not quite ?>sure how to address this. <snip> On 10/06/17 06:22 AM, Jeff King wrote: > On Sat, Jun 10, 2017 at 06:12:28AM -0400, Samuel Lijin wrote: >> On Sat, Jun 10, 2017 at 4:25 AM, Jeff King <peff@xxxxxxxx> wrote: >>> On Wed, Jun 07, 2017 at 06:46:18PM -0400, Houston Fortney wrote: >>> >>>> I sometimes forget about something that I stashed. It would be nice >>>> if the git status command would just say "There are x entries in >>>> the stash." It can say nothing if there is nothing stashed so it is >>>> usually not adding clutter. >>> >>> I think the clutter issue would depend on your workflow around stash. >>> >>> Some people carry tidbits in their stash for days or weeks. E.g., I >>> sometimes start on an idea and decide it's not worth pursuing (or >>> more likely, I post a snippet of a patch as a "how about this" to >>> the mailing list but don't plan on taking it further). Rather than >>> run "git reset --hard", I usually "git stash" the result. That means >>> if I really do decide I want it back, I can prowl through the stash list and find it. >>> >>> All of which is to say that if we had such a feature, it should >>> probably be optional. For some people it would be very useful, and >>> for others it would be a nuisance. >> >> Perhaps there should be a flag for this if it is implemented, say >> status.showStash? Random thought: what if a stash id could be used in the same way as any other ref, so diff stash[0] stash[1] would be possible - although I can see this being problematic for a merge or rebase. Cheers, Randall