Re: [BUG?] Confusion with git stash list
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 21, 2023, 16:33 UTC
- Message-ID
- <xmqqedl1w7ft.fsf@gitster.g>
- In-Reply-To
- <CAPx1GvcxdJhAQA=sDJ7reu+shaeuzz+-xZKOoD0ZNo89hOgmbw@mail.gmail.com>
Chris Torek <chris.torek@gmail.com> writes:
Show 14 quoted lines
> 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`.
I do not think it was intended, but falls within the realm of "do not do it, if it hurts" ;-)