| commit | d4e890e5de1ea7107d8d1b4134ab0144bbf27b8c | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 23 Oct 2007 20:55:32 +0000 (23 16:55 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 23 Oct 2007 22:49:27 +0000 (23 18:49 -0400) | ||
| tree | 544179f241eaaf5e5ec8767987b77141a7c82afd | treesnapshot (tar.gz zip) |
| parent | bbbadf6e58f72ac6bf739d2a1109cbd872eb1083 | commitdiff |
git-gui: Make sure we get errors from git-update-index
I'm seeing a lot of silent failures from git-update-index on
Windows and this is leaving the index.lock file intact, which
means users are later unable to perform additional operations.
When the index is locked behind our back and we are unable to
use it we may need to allow the user to delete the index lock
and try again. However our UI state is probably not currect
as we have assumed that some changes were applied but none of
them actually did. A rescan is the easiest (in code anyway)
solution to correct our UI to show what the index really has
(or doesn't have).
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
I'm seeing a lot of silent failures from git-update-index on
Windows and this is leaving the index.lock file intact, which
means users are later unable to perform additional operations.
When the index is locked behind our back and we are unable to
use it we may need to allow the user to delete the index lock
and try again. However our UI state is probably not currect
as we have assumed that some changes were applied but none of
them actually did. A rescan is the easiest (in code anyway)
solution to correct our UI to show what the index really has
(or doesn't have).
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/index.tcl | diffblobblamehistory |