Re: [PATCH 4/2] t5615-alternate-env: double-quotes in file names do not work on Windows
- From
Jeff King <peff@peff.net>
- Date
- Dec 21, 2016, 22:42 UTC
- Message-ID
- <20161221224222.6fn6irefmd6li6oa@sigill.intra.peff.net>
- In-Reply-To
- <00b6235d-c1bc-30c2-6539-6c78c4ce9eb0@kdbg.org>
On Wed, Dec 21, 2016 at 10:33:43PM +0100, Johannes Sixt wrote:
Show 14 quoted lines
> 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?
-Peff