Re: speeding up cg-log -u

2 messages, 1 author, 2016-06-15 · open the first message on its own page

Re: speeding up cg-log -u

From: Petr Baudis <hidden>
Date: 2016-06-15 22:41:57

Dear diary, on Sat, May 14, 2005 at 08:19:14AM CEST, I got a letter
where Zack Brown [off-list ref] told me that...
Currently cg-log handles this by grabbing all the log data from git, and
then grepping through it.
Which is clearly suboptimal since cg-log now does git-cat-file up to
_three_ times per commit. It should instead process the commit only
once.

Dear diary, on Sat, May 14, 2005 at 11:50:24AM CEST, I got a letter
where Junio C Hamano [off-list ref] told me that...
+	buffer = read_sha1_file(item->object.sha1, type, &size);
If it do that, I wonder how much speedup would be using this instead.
But probably still significant one.

What I don't like is that it searches only the author field. I find the
behaviour that it searches in the committer field as well very useful,
since I can easily check whose patches on a file I checked it - that's
useful when porting own stuff to another branch, or frequently it's the
only thing I actually remember. :-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

Re: speeding up cg-log -u

From: Petr Baudis <hidden>
Date: 2016-06-15 22:41:57

Where was my English? Sorry.
If it do that, I wonder how much speedup would be using this instead.
(does)
But probably still significant one.

What I don't like is that it searches only the author field. I find the
behaviour that it searches in the committer field as well very useful,
since I can easily check whose patches on a file I checked it
(which patches of a file I checked in)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help