| commit | a117fa211671b01449c81c7aed6766e55cb55c38 | |
| author | Csaba Kiraly <kiraly@disi.unitn.it> | |
| Mon, 15 Dec 2014 15:38:00 +0000 (15 16:38 +0100) | ||
| committer | Pat Thoyts <patthoyts@users.sourceforge.net> | |
| Mon, 5 Jan 2015 16:13:25 +0000 (5 16:13 +0000) | ||
| tree | 0f176b4ea00724540d444688065371ec35f635d0 | treesnapshot (tar.gz zip) |
| parent | cdc6aba8c52af4ac4338a1e9fb1028ca3337a5e3 | commitdiff |
git-gui: fix problem with gui.maxfilesdisplayed
gui.maxfilesdisplayed (added in dd6451f9c7c5a36d3006231b618ac6da06c7c7b4)
was applied brute force on the file list in alphabetic order. As a result,
files that had modifications might not be displayed by git-gui. Even
worse, files that are already in the index might not be displayed, which
makes git-gui hard to use in some workflows.
This fix changes the meaning of gui.maxfilesdisplayed, making it a soft
limit that only applies to "_O" files, i.e. files that are "Untracked,
not staged".
Signed-off-by: Csaba Kiraly <kiraly@disi.unitn.it>
Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
gui.maxfilesdisplayed (added in dd6451f9c7c5a36d3006231b618ac6da06c7c7b4)
was applied brute force on the file list in alphabetic order. As a result,
files that had modifications might not be displayed by git-gui. Even
worse, files that are already in the index might not be displayed, which
makes git-gui hard to use in some workflows.
This fix changes the meaning of gui.maxfilesdisplayed, making it a soft
limit that only applies to "_O" files, i.e. files that are "Untracked,
not staged".
Signed-off-by: Csaba Kiraly <kiraly@disi.unitn.it>
Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
| git-gui.sh | diffblobblamehistory |