| commit | a41e45ea1ccc88b4b13af16434c79ffe65ba978a | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 16 Jan 2008 06:29:39 +0000 (16 01:29 -0500) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 16 Jan 2008 06:29:39 +0000 (16 01:29 -0500) | ||
| tree | 396f7e2a3e56b7bdab7d82bc95d57a8095b8ba58 | treesnapshot (tar.gz zip) |
| parent | d36a8f73a4201ab21a553b5caa5b890b8f1d7213 | commitdiff |
git-gui: Refresh file status description after hunk application
If we apply a hunk in either direction this may change the file's
status. For example if a file is completely unstaged, and has at
least two hunks in it and the user stages one hunk the file will
change from "Modified, not staged" to "Portions staged for commit".
Resetting the file path causes our trace on this variable to fire;
that trace is used to update the file header in the diff viewer to
the file's current status.
Noticed by Johannes Sixt.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
If we apply a hunk in either direction this may change the file's
status. For example if a file is completely unstaged, and has at
least two hunks in it and the user stages one hunk the file will
change from "Modified, not staged" to "Portions staged for commit".
Resetting the file path causes our trace on this variable to fire;
that trace is used to update the file header in the diff viewer to
the file's current status.
Noticed by Johannes Sixt.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/diff.tcl | diffblobblamehistory |