Shawn O. Pearce 124355d32c git-gui: Always start a rescan on an empty diff. ...

If we got an empty diff its probably because the modification time of
the file was changed but the file content hasn't been changed.  Typically
this happens because an outside program modified the file and git-gui
was told to not run 'update-index --refresh', as the user generally
trusts file modification timestamps.  But we can also get an empty diff
when a program undos a file change and still updates the modification
timestamp upon saving, but has undone the file back to the same as what
is in the index or in PARENT.

So even if gui.trustmtime is false we should still run a rescan on
an empty diff.  This change also lets us cleanup the dialog message
that we show when this case occurs, as its no longer got anything to
do with Trust File Modification Timestamps.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>

2007-01-23 01:48:50 -05:00

.gitignore

git-gui: Ensure version number is always current.

2007-01-21 02:54:19 -05:00

git-gui.sh

git-gui: Always start a rescan on an empty diff.

2007-01-23 01:48:50 -05:00

GIT-VERSION-GEN

git-gui: Ensure version number is always current.

2007-01-21 02:54:19 -05:00

Makefile

git-gui: Ensure version number is always current.

2007-01-21 02:54:19 -05:00

TODO

git-gui: Update todo list with finished and new items.

2007-01-21 22:47:59 -05:00

Description

Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.

chacktoberfestshell

809 MiB

Languages

C 50.1%

Shell 38.4%

Perl 5.1%

Tcl 3.2%

Python 0.8%

Other 2.1%