Re: [BUG?] Confusion with git stash list

From: Chris Torek <chris.torek@gmail.com>
Date: Jul 21, 2023, 16:09 UTC
Message-ID: <CAPx1GvcxdJhAQA=sDJ7reu+shaeuzz+-xZKOoD0ZNo89hOgmbw@mail.gmail.com>
In-Reply-To: <046c01d9bbeb$a8680bc0$f9382340$@nexbridge.com>

On Fri, Jul 21, 2023 at 9:05 AM <rsbecker@nexbridge.com> wrote:

> It is simple to set up. You do need at least one stash, but the contents are
> irrelevant. So given any repository, use git stash push. Then use git stash
> list --all.

The `git stash list` command is secretly just a front end to `git log` that inserts particular options, so `--all` is passed to `git log` and does what it does. That's why you see what you see (remember that `git stash list` includes `-g` / `--walk-reflogs` so `--all` here means "all reflogs").

Whether this is *intended* is another question, but to stop it, `git stash` would have to notice and alter / remove `--all` before passing the rest of the command on to `git log`.

Chris