From: erik88 <erik88@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Patrick Steinhardt" <ps@pks.im>,
"Emin Özata via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Greg Hewgill" <greg@hewgill.com>,
"Micheil Smith" <micheil@brandedcode.com>,
"Michael Haggerty" <mhagger@alum.mit.edu>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Emin Özata" <eminozata@proton.me>
Subject: Re: [PATCH] stash: add 'rename' subcommand
Date: Sun, 26 Jul 2026 11:00:42 +0200 [thread overview]
Message-ID: <amXJcVadL8btF_gh@vader> (raw)
In-Reply-To: <xmqqpl0mbetb.fsf@gitster.g>
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.
> 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 ;-)
prev parent reply other threads:[~2026-07-26 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 8:31 [PATCH] stash: add 'rename' subcommand Emin Özata via GitGitGadget
2026-07-16 10:08 ` Patrick Steinhardt
2026-07-16 17:46 ` Junio C Hamano
2026-07-16 21:08 ` brian m. carlson
2026-07-17 1:11 ` Junio C Hamano
2026-07-26 9:00 ` erik88 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=amXJcVadL8btF_gh@vader \
--to=erik88@gmail.com \
--cc=avarab@gmail.com \
--cc=eminozata@proton.me \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=greg@hewgill.com \
--cc=mhagger@alum.mit.edu \
--cc=micheil@brandedcode.com \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox