From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Kyle Meyer <kyle@kyleam.com>, Tassilo Horn <tsdh@gnu.org>,
Tao Klerks <tao@klerks.biz>,
git@vger.kernel.org
Subject: Re: [BUG?] Major performance issue with some commands on our repo's master branch
Date: Thu, 09 Jun 2022 11:23:58 -0700 [thread overview]
Message-ID: <xmqqedzxlmpt.fsf@gitster.g> (raw)
In-Reply-To: <YqILyX97zKg5ViUS@coredump.intra.peff.net> (Jeff King's message of "Thu, 9 Jun 2022 11:03:37 -0400")
Jeff King <peff@peff.net> writes:
> git show --diff-filter=D -s a6434bc6f7a1
>
> Without the patch above, it always shows the commit. With it, it shows
> nothing. That's a bit far-fetched, but it is a regression, and I'm also
> not sure if it's just the tip of the iceberg.
Here "-s" is merely "do not give patch output like we do by
default", so the behaviour is quite understandable and is not a
regression we would want to see happen. -S/-G are also likely to be
affected, not just the --diff-filter.
> It also doesn't solve problem completely. Regular commits can have
> expensive diffs, too.
That's a good point.
> I think you'd do better to have a mode specific to git-show that skips
> the diff if we're not showing it, but makes sure to always show the
> commit anyway.
Meaning an explicit option "git show --log-only"? We'd need to
careful to make it either (1) be incompatible with certain features
of "git show" (like giving a pathspec) and error out, or (2) ignore
these features of "git show" silently and document that. But it
would work as a new option.
Thanks.
next prev parent reply other threads:[~2022-06-09 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 7:39 [BUG?] Major performance issue with some commands on our repo's master branch Tassilo Horn
2022-06-04 20:20 ` Tao Klerks
2022-06-05 10:46 ` Tassilo Horn
2022-06-06 5:18 ` Tao Klerks
2022-06-08 23:36 ` Jeff King
2022-06-09 1:27 ` Kyle Meyer
2022-06-09 15:03 ` Jeff King
2022-06-09 18:23 ` Junio C Hamano [this message]
2022-06-09 18:43 ` Jeff King
2022-06-09 20:06 ` Junio C Hamano
2022-06-09 5:51 ` Tassilo Horn
2022-06-09 15:05 ` Jeff King
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=xmqqedzxlmpt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kyle@kyleam.com \
--cc=peff@peff.net \
--cc=tao@klerks.biz \
--cc=tsdh@gnu.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;
as well as URLs for NNTP newsgroup(s).