Re: cmd: Don't parse colons as stream separators when splitting paths.

2011-08-30 Thread Frédéric Delanoy
2011/8/30 Octavian Voicu : > 2011/8/29 Octavian Voicu >> >> Alexandre already committed the patch, so if native passes the test I can >> send a test for the next iteration. On the other hand, if native chokes on >> the colon, then we shouldn't add any testcases. If it works, might also >> throw a

Re: cmd: Don't parse colons as stream separators when splitting paths.

2011-08-29 Thread Octavian Voicu
2011/8/29 Octavian Voicu > Alexandre already committed the patch, so if native passes the test I can > send a test for the next iteration. On the other hand, if native chokes on > the colon, then we shouldn't add any testcases. If it works, might also > throw a @pwd@ in there. > I've got the res

Re: cmd: Don't parse colons as stream separators when splitting paths.

2011-08-29 Thread Octavian Voicu
2011/8/29 Frédéric Delanoy > Might be a good idea to add a simple testcase > Not sure yet how native is going to handle this, because windows doesn't allow colons in filenames. I submitted a job to the testbot to check this [1]. Alexandre already committed the patch, so if native passes the tes

Re: cmd: Don't parse colons as stream separators when splitting paths.

2011-08-29 Thread Frédéric Delanoy
On Sun, Aug 28, 2011 at 00:39, Octavian Voicu wrote: > Fixes an infinite recursion when running a command such as "del file.txt /S" > in a directory that has some subdirectory with a colon in its name. > > The filename:stream syntax can be used on native to access alternate data > streams on NTFS