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

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 27, 2026, 05:45 UTC
Message-ID: <xmqqtsplouii.fsf@gitster.g>
In-Reply-To: <amXJcVadL8btF_gh@vader>

erik88 <erik88@gmail.com> writes:

Show 14 quoted lines

> On 26/07/16 06:11PM, Junio C Hamano wrote:
>> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>>
>> > 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).

>> 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 ;-).