On 2016-03-22 18.43, Johannes Schindelin wrote: > These two tests wanted to write file names which are incompatible with > Windows' file naming rules. > > Signed-off-by: Johannes Schindelin <johannes.schinde...@gmx.de>
Is there a chance to squeeze in a precondition for HFS under Mac OS ? > -test_expect_success UTF8 'svn.pathnameencoding=cp932 new file on dcommit' ' > +test_expect_success UTF8,!MINGW 'svn.pathnameencoding=cp932 new file on > dcommit' ' +test_expect_success UTF8,!MINGW,!UTF8_NFD_TO_NFC > LC_ALL=$a_utf8_locale && > export LC_ALL && > neq=$(printf "\201\202") && > @@ -105,7 +105,7 @@ test_expect_success UTF8 'svn.pathnameencoding=cp932 new > file on dcommit' ' > ' > > # See the comment on the above test for setting of LC_ALL. > -test_expect_success 'svn.pathnameencoding=cp932 rename on dcommit' ' > +test_expect_success !MINGW 'svn.pathnameencoding=cp932 rename on dcommit' ' And the same protection for HFS here. Question: Why do we need a UTF8 protection in #11, but not in #12 ? I just tested t9115 under german cygwin, passes. http://article.gmane.org/gmane.comp.version-control.git/288827 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
