| commit | 38cda0b0decd135fea7fcfc7fce75ab62e819c09 | |
| 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> | |
| Mon, 12 Apr 2010 12:56:16 +0000 (12 14:56 +0200) | ||
| tree | 3bac0f6fd959d198cb34f88bf54c5fad05fe53d0 | treesnapshot (tar.gz zip) |
| parent | 6f75a58a47a75d4ef5029128e031547c71e202bc | 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 |