From: Junio C Hamano <gitster@pobox.com>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Cc: Yuri <yuri@rawbw.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Make 'git stash list' more informative
Date: Mon, 07 Apr 2025 22:06:20 +0000 [thread overview]
Message-ID: <xmqqiknflj8j.fsf@gitster.g> (raw)
In-Reply-To: <29E4ED32-4909-48EF-86BB-67111B62AE1A@gmail.com> (Lucas Seiki Oshiro's message of "Sat, 5 Apr 2025 13:24:02 -0300")
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
>> It contains the last commit's subject which often/usually doesn't
>> really describe the stash entry.
It depends on how you work.
I do agree that the work recorded in the stash entries tend to be
pretty much unrelated to the work I was doing on the branch (hence
the theme of the base commit). After all, if they are related,
you're more likely not keeping the work in the stash entries---you'd
rather be making completed commit on the branch.
However, I find that the subject of the base commit the stashed work
was derived from works well as a memory aid to recall what I was
working on when the stash entry was created.
So "doesn't really describe" is correct, but because stash is by
design a local thing, it is not a failure that it "doesn't really
describe"---the purpose of the message is to be something easily
generated and help jog your memory later.
Having said that ...
> `git stash list` accepts the options from `git log`, so you can change
> look at its manpage to find other options that show the information
> that you want.
... this is an excellent suggestion.
Thanks.
next prev parent reply other threads:[~2025-04-07 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 4:12 Make 'git stash list' more informative Yuri
2025-04-05 16:24 ` Lucas Seiki Oshiro
2025-04-07 22:06 ` Junio C Hamano [this message]
2025-04-08 2:06 ` Lucas Seiki Oshiro
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=xmqqiknflj8j.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lucasseikioshiro@gmail.com \
--cc=yuri@rawbw.com \
/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