From: Yuri <yuri@rawbw.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Make 'git stash list' more informative
Date: Fri, 4 Apr 2025 21:12:26 -0700 [thread overview]
Message-ID: <edcd6174-e931-4ab9-b61d-8126a6cab740@rawbw.com> (raw)
Currently 'git stash list' prints lines like this:
stash@{10}: WIP on main: 3f802b772d88 science/py-pymatgen: update
2025.1.24 → 2025.2.18
It contains the last commit's subject which often/usually doesn't really
describe the stash entry.
I propose to amend WIP stash entry descriptions with size, number of
dirs and files, and time description, so that the above entry might look
like this:
stash@{10}: WIP on main: 3f802b772d88 science/py-pymatgen: update
2025.1.24 → 2025.2.18 (+20, -5, 3 dirs, 5 files, 17 days ago)
It would add info about the number of changed lines, number of affected
directories and files, and how old this stash record is.
This would make WIP stash lines much more informative and they would
actually describe better what is in them.
Thanks,
Yuri
next reply other threads:[~2025-04-05 4:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 4:12 Yuri [this message]
2025-04-05 16:24 ` Make 'git stash list' more informative Lucas Seiki Oshiro
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=edcd6174-e931-4ab9-b61d-8126a6cab740@rawbw.com \
--to=yuri@rawbw.com \
--cc=git@vger.kernel.org \
/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