From: linux@horizon.com
To: linux-kernel@vger.kernel.org, pasky@suse.cz
Subject: Re: Linux v2.6.17
Date: 19 Jun 2006 03:41:47 -0400 [thread overview]
Message-ID: <20060619074147.11641.qmail@science.horizon.com> (raw)
>> [torvalds@g5 linux]$ time git log v2.6.16..v2.6.17 > /dev/null
>>
>> real 0m0.484s
>> user 0m0.448s
>> sys 0m0.036s
>>
>> ie the logfile generation really is almost free. And yes, that's the
>> _full_ big log (all 92 _thousand_ lines of it, from the 6113 commits in
>> the 2.6.16->17 case) being generated in under half a second.
> I assume that this is with hot cache, which is something you shouldn't
> assume for a use like this - you likely aren't in the middle of doing
> stuff with the repository but just want to peek at the changes list.
Okay, a laptop with a cold cache:
$ time git log v2.6.16..v2.6.17 > /dev/null
real 0m2.815s
user 0m1.264s
sys 0m0.044s
And, just for fun, having warmed the cache with that:
$ time git log v2.6.12..v2.6.17 > /dev/null
real 0m2.343s
user 0m1.656s
sys 0m0.068s
All 368519 lines (14 MB) of it. I have to hand it to Linus,
when you say "git", it gits.
(On a not very related point having to do with git and the kernel,
I usually edit the root Makefile to set INSTALL_PATH to where I want
"make bzlilo" to put it, but this results in my kernels being named
v.2.6.17-dirty. I can set INSTALL_PATH by hand on the command line,
except when I forget and waste a reboot. I can't install a symlink,
because the install provess renames the symlink. Is there an easy way
to semi-permanently change INSTALL_PATH without triggering the -dirty
detection? Create a GNUmakefile that includes the Makefile?)
next reply other threads:[~2006-06-19 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:41 linux [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-18 1:59 Linus Torvalds
2006-06-18 2:06 ` Linus Torvalds
2006-06-18 3:30 ` Brice Goglin
2006-06-18 3:47 ` Linus Torvalds
2006-06-19 1:39 ` Petr Baudis
2006-06-18 13:49 ` Adrian Bunk
2006-06-18 16:44 ` Linus Torvalds
2006-06-19 21:25 ` Adrian Bunk
2006-06-19 14:23 ` Mark Lord
2006-06-18 10:54 ` Michael Buesch
2006-06-18 16:47 ` Andre Tomt
2006-06-18 17:05 ` Michael Buesch
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=20060619074147.11641.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@suse.cz \
/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
all inboxes | Powered by JetHome®