From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Bruno Haible <bruno@clisp.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: how to speed up "git log"?
Date: Mon, 12 Feb 2007 01:28:13 -0500 [thread overview]
Message-ID: <20070212062813.GE699@spearce.org> (raw)
In-Reply-To: <20070212062224.GD699@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> wrote:
> Junio C Hamano <junkio@cox.net> wrote:
> > "Shawn O. Pearce" <spearce@spearce.org> writes:
> > > So I ran three trials, v1.5.0-rc4-26-gcc46a74 with and without
> > > NO_MMAP against v1.4.4.4 on a freshly repacked git.git.
I probably should have mentioned, my run (in all cases) was:
git rev-list HEAD -- Makefile 2>/dev/null
cheap, a file that exists pretty much everywhere, and that triggers
the path limiter in the revision walking code.
BTW, I discovered by accident tonight that this works:
cp git-rev-list ../git-1444
../git-1444 rev-list
which is so not something I would have expected. :-) I honestly
expected the wrapper to puke and say it doesn't know what command
1444 is.
--
Shawn.
next prev parent reply other threads:[~2007-02-12 6:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 11:52 how to speed up "git log"? Bruno Haible
2007-02-11 16:49 ` Johannes Schindelin
2007-02-11 23:00 ` Shawn O. Pearce
2007-02-11 23:08 ` Johannes Schindelin
2007-02-11 23:41 ` Bruno Haible
2007-02-11 23:46 ` Shawn O. Pearce
2007-02-11 23:56 ` Johannes Schindelin
2007-02-11 23:59 ` Robin Rosenberg
2007-02-12 2:02 ` Bruno Haible
2007-02-12 11:19 ` Johannes Schindelin
2007-02-12 4:08 ` Junio C Hamano
2007-02-12 6:06 ` Shawn O. Pearce
2007-02-12 6:11 ` Junio C Hamano
2007-02-12 6:22 ` Shawn O. Pearce
2007-02-12 6:28 ` Shawn O. Pearce [this message]
2007-02-12 4:20 ` Linus Torvalds
2007-02-12 11:27 ` Bruno Haible
[not found] ` <20070211152840.GA2781@steel.home>
2007-02-11 23:52 ` Bruno Haible
2007-02-17 19:19 ` Bruno Haible
2007-02-17 23:20 ` Johannes Schindelin
2007-02-18 0:09 ` piped to a pager (was: how to speed up "git log"?) Bruno Haible
2007-02-18 0:10 ` Johannes Schindelin
2007-02-18 6:33 ` how to speed up "git log"? Shawn O. Pearce
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=20070212062813.GE699@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bruno@clisp.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=robin.rosenberg.lists@dewire.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;
as well as URLs for NNTP newsgroup(s).