Skip to contentSkip to conversation

Linux v2.6.17

DISCUSSION [email protected] 1 participant 1 message Jun 19, 2006

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines
Quoted 6 lines
	[torvalds@g5 linux]$ time git log v2.6.16..v2.6.17 > /dev/null 
	
	real    0m0.484s
	user    0m0.448s
	sys     0m0.036s
Quoted 7 lines
Quoted 3 lines

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?)