From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [Q] Where does "git commit -q -m msg" spend time?
Date: Fri, 18 Nov 2022 15:37:29 -0800 [thread overview]
Message-ID: <xmqqbkp3kf5y.fsf@gitster.g> (raw)
On a slow filesystem it gets more noticeable, but I have been
wondering (without a debugger or a profiler, as I am supposed to be
on vacation) for the past few weeks why these two commands in the
same repository perform very differently:
$ git write-tree
$ git commit -q -m msg
Especially even after running the former, running the latter, which
I naïvely thought that it only needs to create a commit object with
"msg" and wrapping the result of the former (which is more-or-less
instant) into it, and do nothing else.
reply other threads:[~2022-11-19 0:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xmqqbkp3kf5y.fsf@gitster.g \
--to=gitster@pobox.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).