On Sunday 28 October 2007, Paul Mackerras wrote: > * Gitk now uses a new graph layout algorithm, which means it doesn't > have to generate the whole layout from top to bottom at startup > time, making startup faster. This is probably causing gitk to eat my (admittedly old) CPU, sometimes. For example, a gitk --all v1.5.2..v1.5.3 gives me problems when I scroll down to about half of the shown history: that is when I reach the sequence of hundreds of "merge topic branch into next" commits, and gitk tries hard to display the graph as best as it can. It can become unresponsive for one second at every PgDown. Otherwise, gitk is way faster in other (non-pathological) circumstances. - 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
