Revision 567c53d00f194a2826dda0b6be5d66283138377d authored by Johannes Schindelin on 03 January 2018, 16:54:50 UTC, committed by Junio C Hamano on 03 January 2018, 23:55:48 UTC
It is totally legitimate to clone Git's source code anywhere, including into, say, directories whose name (or the name of its absolute path) contains spaces. However, a couple of tests failed to anticipate this, for lack of quoting (or in one instance, for failure to expect more than one space in the absolute path of the TEST_DIRECTORY). This can be easily verified by calling these commands in your current clone: git clone . with\ spaces cd with\ spaces make -j15 test Let's fix this. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Reviewed-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 42e6fde
File | Mode | Size |
---|---|---|
static | ||
INSTALL | -rw-r--r-- | 14.4 KB |
Makefile | -rw-r--r-- | 5.5 KB |
README | -rw-r--r-- | 2.3 KB |
gitweb.perl | -rwxr-xr-x | 246.5 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...