Thread (11 messages) flat view 11 messages, 6 authors, 6d ago

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

From: Junio C Hamano <hidden>
Date: 2026-07-27 05:45:45

erik88 [off-list ref] writes:
On 26/07/16 06:11PM, Junio C Hamano wrote:
quoted
"brian m. carlson" [off-list ref] writes:
quoted
I have a large number of stashes in my git.git repository (211 at
present) and it may be that I, in a mad rush to solve some problem or
another, went with the default message.  I do this kind of thing with
repositories at work all the time.  But it's inconvenient to have to
search through `git stash list -p` to see which change it was and which
stash I need to pop to resume my work, so I can see the utility of this
approach.
Same. I always accumulate 100+ stashes. I never bother with a message
when I stash. 90-95% of the stashes are useless cruft but there's always
an experiment, a script file of some sort, which turns out to be useful.
OK, so editing the log message for each stash entry is already a use
case.  In that case, I no longer object to the feature in principle.
At least, I cannot think of a way for it to encourage any bad
workflows.

The next step is for someone to review the implementation.  I have
not read the implementation at all, and it will be quite a while
until I get to it (if I ever do).
quoted
Hmph, are you saying that you are going to wade through 211
stash entries one by one and reword them?
Not me but my AI agent ;-)
I have no sympathy for you, then.  Your AI agent should be able to
unstash and restash 211 entries one by one and reword them just fine
;-).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help