From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Peter Kassak" <cache.sk@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Extremely long subtree split duration
Date: Fri, 29 Nov 2024 20:50:55 +0100 [thread overview]
Message-ID: <1b5f05ce-6e91-4f90-b3ff-f7cedfa32586@app.fastmail.com> (raw)
In-Reply-To: <1c026a82-d24b-48f0-8206-47c2eeed1442@app.fastmail.com>
I don’t use this command and I am an outsider to the code (to all of the
code in this project). But the commit that introduced this apparent
performance regression does a lot of `git log -1` calls. Very apparent
when I ran it since I got a lot of stderr output about missing note refs
(since I use them in another project).
For what it’s worth.
prev parent reply other threads:[~2024-11-29 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 21:40 Extremely long subtree split duration Peter Kassak
2024-11-08 22:07 ` Kristoffer Haugsbakk
2024-11-09 14:27 ` Kristoffer Haugsbakk
2024-11-09 21:10 ` Peter Kassak
2024-11-29 19:44 ` Kristoffer Haugsbakk
2024-11-29 19:50 ` Kristoffer Haugsbakk [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=1b5f05ce-6e91-4f90-b3ff-f7cedfa32586@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=cache.sk@gmail.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;
as well as URLs for NNTP newsgroup(s).