> From: Corinna Vinschen
[snip Cygwin non-POSIXness, which unless I'm delirious used to be a big deal
to the Cygwin PTB]
> My point is that I'm happy to make Cygwin mostly POSIX
> compatible, but that implementing all crude border cases
> sometimes has more negative impact in other areas (one o
On Oct 25 20:02, Eric Blake wrote:
> According to Corinna Vinschen on 10/25/2005 7:27 AM:
> > And I really can't see how "one testcase fails because Cygwin allows
> > something which should fail according to POSIX" qualifies for "coreutils
> > doesn't work out of the box on Cygwin". Does the coreu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 10/25/2005 7:27 AM:
>>I would much rather see a fix in cygwin so that coreutils would work out
>>of the box in this case.
>>
>
> And I really can't see how "one testcase fails because Cygwin allows
> something which sh
On Oct 25 07:07, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The fact that cygwin incorrectly flattens /name/../ to / in pathname
> resolution without first resolving name is triggering a failure in a new
> test recently added to the coreutils testsuite.
>
> mkdir -p d
4 matches
Mail list logo
