From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: Yuri <yuri@rawbw.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Make 'git stash list' more informative
Date: Sat, 5 Apr 2025 13:24:02 -0300 [thread overview]
Message-ID: <29E4ED32-4909-48EF-86BB-67111B62AE1A@gmail.com> (raw)
In-Reply-To: <edcd6174-e931-4ab9-b61d-8126a6cab740@rawbw.com>
> It contains the last commit's subject which often/usually doesn't really describe the stash entry.
`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.
> I propose to amend WIP stash entry descriptions with size, number of dirs and files
Perhaps this helps you:
`git stash list --stat --pretty=reference`
You can customize following the format described on https://git-scm.com/docs/pretty-formats.
> Thanks,
> Yuri
I hope it helps you!
next prev parent reply other threads:[~2025-04-05 16:39 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 [this message]
2025-04-07 22:06 ` Junio C Hamano
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=29E4ED32-4909-48EF-86BB-67111B62AE1A@gmail.com \
--to=lucasseikioshiro@gmail.com \
--cc=git@vger.kernel.org \
--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