| commit | 1cad232f92794834c8e70dfc0a1f35431d2c05cd | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 8 Oct 2007 01:12:31 +0000 (7 18:12 -0700) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 10 Oct 2007 05:12:17 +0000 (10 01:12 -0400) | ||
| tree | 131b66c3727f36aad3b8786cd5d655707df6a817 | treesnapshot (tar.gz zip) |
| parent | 51e1eadb7cd9c8b1943fdc62fe28535bfc032fc6 | commitdiff |
git-gui: Use progress meter in the status bar during index updates
If we are updating the index to stage or unstage changes or reverting
files in the working directory we can use the progress handling parts
of our status bar to perform this display work, reducing the amount of
code duplication we have in the index handling module.
Unfortunately the status bar is still a strict approximation as it is
unable to know when git-update-index has processed the data we fed to
it. The progress bar is actually a progress of the pipe buffer filling
up in the OS, not of the actual work done. Still, it tells the user we
are working and that has some value.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
If we are updating the index to stage or unstage changes or reverting
files in the working directory we can use the progress handling parts
of our status bar to perform this display work, reducing the amount of
code duplication we have in the index handling module.
Unfortunately the status bar is still a strict approximation as it is
unable to know when git-update-index has processed the data we fed to
it. The progress bar is actually a progress of the pipe buffer filling
up in the OS, not of the actual work done. Still, it tells the user we
are working and that has some value.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/index.tcl | diffblobblamehistory |