From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Yuri <yuri@rawbw.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [feature suggestion] Improve stash descriptions
Date: Mon, 26 Apr 2021 12:14:07 -0400 [thread overview]
Message-ID: <YIbmz2BUKV0/pcIB@coredump.intra.peff.net> (raw)
In-Reply-To: <87r1ix4dsc.fsf@evledraar.gmail.com>
On Mon, Apr 26, 2021 at 11:00:57AM +0200, Ævar Arnfjörð Bjarmason wrote:
> >> In case many directories are affected it could say "changes are in
> >> path1/dir1, path2/dir2, etc."
> >
> > This is unfortunately not going to be very efficient to compute in
> > certain cases, such as with large working trees where there are many
> > changes. So while it would improve the automated stash message, it
> > might also make stashing much slower on large repositories.
>
> Just to add to this, there's already:
>
> git stash list [--stat|--numstat|--shortstat]
>
> It seems to me that what's being requested here is not so much a
> stash-specific feature, but some abbreviated "human readable" stat
> format that could be used with any log-like command.
There's also --dirstat, which will summarize the impacted directories
(though it does not say much useful if the entries are all in the root,
as they typically are for git.git).
-Peff
prev parent reply other threads:[~2021-04-26 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 21:16 [feature suggestion] Improve stash descriptions Yuri
2021-04-25 17:17 ` brian m. carlson
2021-04-26 9:00 ` Ævar Arnfjörð Bjarmason
2021-04-26 16:14 ` Jeff King [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=YIbmz2BUKV0/pcIB@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--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