Re: [PATCH 4/2] t5615-alternate-env: double-quotes in file names do not work on Windows
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Dec 22, 2016, 06:13 UTC
- Message-ID
- <4e66fba1-d881-6a96-1e4d-da9c897353ac@kdbg.org>
- In-Reply-To
- <20161221224222.6fn6irefmd6li6oa@sigill.intra.peff.net>
Am 21.12.2016 um 23:42 schrieb Jeff King:
Show 19 quoted lines
> On Wed, Dec 21, 2016 at 10:33:43PM +0100, Johannes Sixt wrote: > >> Protect a recently added test case with !MINGW. >> >> Signed-off-by: Johannes Sixt <j6t@kdbg.org> >> --- >> I don't remember why I did not notice this failure sooner. >> Perhaps I did, but then ran out of time to debug it... >> >> The patch should go on top of jk/quote-env-path-list-component. >> [...] >> -test_expect_success 'broken quoting falls back to interpreting raw' ' >> +test_expect_success !MINGW 'broken quoting falls back to interpreting raw' ' >> mv one.git \"one.git && >> check_obj \"one.git/objects <<-EOF >> $one blob > > Hmph. I explicitly avoided a colon in the filename so that it would run > on MINGW. Is a double-quote also not allowed?
It is not allowed; that was my conclusion. But now that you ask, I'll double-check.
-- Hannes