Long-standing problem in one of the corner cases of rename(2): If we rename a directory a check is performed to see if newpath is identical to oldpath or a subdir of oldpath. This check is (accidentally? no hints anywhere in ChangeLogs or code) performed case-insensitive for as long as we use Unicode paths and NT functions. This leads to the problems described in https://cygwin.com/ml/cygwin/2016-09/msg00264.html Change this to be conditional case-sensitive as all other checks but let's take this with a grain of salt. There may be corner-cases in this corner-case which require to chek parts of the path always case-insensitive. Off the top of my head I can't construct such a case but that's no proof they don't exist :} Signed-off-by: Corinna Vinschen <corinna@vinschen.de> |
||
---|---|---|
.. | ||
1.7.10 | ||
1.7.11 | ||
1.7.12 | ||
1.7.13 | ||
1.7.14 | ||
1.7.15 | ||
1.7.16 | ||
1.7.17 | ||
1.7.18 | ||
1.7.19 | ||
1.7.20 | ||
1.7.21 | ||
1.7.22 | ||
1.7.23 | ||
1.7.24 | ||
1.7.25 | ||
1.7.26 | ||
1.7.27 | ||
1.7.28 | ||
1.7.29 | ||
1.7.30 | ||
1.7.31 | ||
1.7.32 | ||
1.7.33 | ||
1.7.34 | ||
1.7.35 | ||
2.0.0 | ||
2.0.1 | ||
2.0.3 | ||
2.0.4 | ||
2.1.0 | ||
2.2.0 | ||
2.2.1 | ||
2.3.0 | ||
2.3.1 | ||
2.4.0 | ||
2.4.1 | ||
2.5.0 | ||
2.5.1 | ||
2.5.2 | ||
2.6.0 | ||
2.6.1 |