On Sun, 4 Nov 2007, Paul Mackerras wrote: > > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
