Re: [RFC PATCH] Make gitk use --early-output

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Nov 4, 2007, 05:30 UTC
Message-ID: <alpine.LFD.0.999.0711032227420.15101@woody.linux-foundation.org>
In-Reply-To: <18221.2285.259487.655684@cargo.ozlabs.ibm.com>

On Sun, 4 Nov 2007, Paul Mackerras wrote:

Show 13 quoted lines

>
> This makes gitk use the --early-output flag on the git log command.
> 
> When gitk sees the "Final output:" line from git log, it goes into a
> mode where it basically just checks that it is getting the commits
> again in the same order as before.  If they are, well and good; if
> not, it truncates its internal list at the point of difference and
> proceeds to read in the commits in the new order from there on, and
> re-does the graph layout if necessary.
> 
> This gives a much more immediate feel to the startup; gitk shows its
> window with the first screenful of commits displayed very quickly this
> way.

Goodie. Seems to work for me. I'll tweak the behaviour of --early-output a bit more, because right now if things are really cold in the cache, the "--early-output" logic will often trigger with just a single commit in the list (because the timeout is so short), but it already seems to work pretty well.

		Linus