author | Shawn O. Pearce <spearce@spearce.org> | |
Sat, 18 Nov 2006 08:03:16 +0000 (03:03 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Sat, 18 Nov 2006 08:03:16 +0000 (03:03 -0500) | ||
commit | 32e0bcab59334ed8f1955c8afa830de22362c1ec | |
tree | 345986be9fe047dbde5696eef651515eb4d85474 | tree | snapshot |
parent | 4539eacd6dde87b4e73c859e946bb0a2c89d71f4 | commit | diff |
git-gui: Only reshow diff when really necessary.
I noticed that we were reshowing the current diff during a commit;
this occurs because we feed every added and modified file through
update-index just before commit. During the update-index process
we reshow the current diff if the current file in the diff pane
was one of those added or modified files we reprocessed. This
just slows down the UI more than is necessary.
So refactoring update_index so that we don't call reshow_diff
from within that code; instead we do it at a higher level.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
I noticed that we were reshowing the current diff during a commit;
this occurs because we feed every added and modified file through
update-index just before commit. During the update-index process
we reshow the current diff if the current file in the diff pane
was one of those added or modified files we reprocessed. This
just slows down the UI more than is necessary.
So refactoring update_index so that we don't call reshow_diff
from within that code; instead we do it at a higher level.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui | diff | blob | history |