| commit | 5440df44c268e718a79a35df6f5d912b21b73ffa | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Thu, 17 Jan 2019 20:14:47 +0000 (17 12:14 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 18 Jan 2019 21:12:14 +0000 (18 13:12 -0800) | ||
| tree | 8307ef1c05bcddba3b1ec3e6484c76f165bcf8ca | treesnapshot (tar.gz zip) |
| parent | 77556354bb7ac50450e3b28999e3576969869068 | commitdiff |
mingw (t5580): document bug when cloning from backslashed UNC paths
Due to a quirk in Git's method to spawn git-upload-pack, there is a
problem when passing paths with backslashes in them: Git will force the
command-line through the shell, which has different quoting semantics in
Git for Windows (being an MSYS2 program) than regular Win32 executables
such as git.exe itself.
The symptom is that the first of the two backslashes in UNC paths of the
form \\myserver\folder\repository.git is *stripped off*.
Document this bug by introducing a test case.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Due to a quirk in Git's method to spawn git-upload-pack, there is a
problem when passing paths with backslashes in them: Git will force the
command-line through the shell, which has different quoting semantics in
Git for Windows (being an MSYS2 program) than regular Win32 executables
such as git.exe itself.
The symptom is that the first of the two backslashes in UNC paths of the
form \\myserver\folder\repository.git is *stripped off*.
Document this bug by introducing a test case.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5580-clone-push-unc.sh | diffblobblamehistory |