Revision 7cf4566f48b7f17c68ab215a9ca6ef7792d9d791 authored by Alexander Gavrilov on 16 November 2008, 18:46:48 UTC, committed by Shawn O. Pearce on 16 November 2008, 21:33:09 UTC
The rescan function receives a callback command as its parameter, which is supposed to be executed after the scan finishes. It is generally used to update status. However, rescan may initiate a loading of a diff, which always calls ui_ready after completion. If the after handler is called before that, ui_ready will override the new status. This commit ensures that the after callback is properly threaded through the diff machinery. Since it uncovered the fact that force_first_diff actually didn't work due to an undeclared global variable, and the desired effects appeared only because of the race condition between the diff system and the rescan callback, I also reimplement this function to make it behave as originally intended. Signed-off-by: Alexander Gavrilov <angavrilov@gmail.com> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
1 parent 153ad78
| File | Mode | Size |
|---|---|---|
| lib | ||
| macosx | ||
| po | ||
| windows | ||
| .gitattributes | -rw-r--r-- | 84 bytes |
| .gitignore | -rw-r--r-- | 97 bytes |
| GIT-VERSION-GEN | -rwxr-xr-x | 1.8 KB |
| Makefile | -rw-r--r-- | 11.2 KB |
| git-gui--askpass | -rwxr-xr-x | 1.3 KB |
| git-gui.sh | -rwxr-xr-x | 82.5 KB |
Computing file changes ...
