| commit | f9c077789e824c98d138fbd3c17e17de57770fd2 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Tue, 11 Aug 2009 00:22:33 +0000 (11 02:22 +0200) | ||
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Wed, 28 Apr 2010 14:24:58 +0000 (28 16:24 +0200) | ||
| tree | 0aa0ddd5bdd8c0104e232f9e6831e7c4a46fa77a | treesnapshot (tar.gz zip) |
| parent | 959d8d90b75ea7834fee021a971048d46f2bc78f | commitdiff |
gitk: work around ridiculous command line restriction on Windows
On Windows, there are dramatic problems when a command line grows
beyond PATH_MAX, which is restricted to 8191 characters on XP and
later (according to http://support.microsoft.com/kb/830473).
Work around this by just cutting off the command line at that length
(actually, at a space boundary) in the hope that only negative
refs are chucked: gitk will then do unnecessary work, but that is
still better than flashing the gitk window and exiting with exit
status 5 (which no Windows user is able to make sense of).
This fixes msysGit issue 387.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
On Windows, there are dramatic problems when a command line grows
beyond PATH_MAX, which is restricted to 8191 characters on XP and
later (according to http://support.microsoft.com/kb/830473).
Work around this by just cutting off the command line at that length
(actually, at a space boundary) in the hope that only negative
refs are chucked: gitk will then do unnecessary work, but that is
still better than flashing the gitk window and exiting with exit
status 5 (which no Windows user is able to make sense of).
This fixes msysGit issue 387.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
| gitk-git/gitk | diffblobblamehistory |