Re: [PATCH] stash: add 'rename' subcommand

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 16, 2026, 17:46 UTC
Message-ID: <xmqqh5lyhlp6.fsf@gitster.g>
In-Reply-To: <alitkCsplW_DIaRw@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 5 quoted lines

> Hm. It's good to refer to to previous discussions. But I think it would
> make sense to also document why explicitly _you_ want to have this
> functionality. Like, what use case does it enable that you currently
> cannot have right now? How is this different to what was proposed back
> then that should make us reconsider whether or not to include it now?

We have one previous discussion thread on this, and there is no need to refer to every single message in it. Just pointing to the discussion starter should be enough to let us read what was said. It was also very nice of Emin to summarize the viewpoints expressed there, so that readers can follow along without having to dig up external resources.

Asking for the actual use case is indeed very useful, and I highly appreciate the nudge.

"I cannot reword the message shown in 'git stash list' without this change" is not a use case. It would be far more useful to know what real-world task you are blocked from accomplishing just because you cannot reword a misspelled entry in 'git stash list'.

Personally, I cannot think of any such roadblock. If I find that a stash entry is worth tweaking right now, I would probably create a new branch for the task, unstash it there, and either make further changes or record the exact state with an updated message to help my future self. After all, having a branch I can start working on immediately is far more useful than having the same stash entry with its spelling corrected.

Thanks.