On 03/15/2016 02:59 AM, Eric Wong wrote:
[]
I just edited locally and pushed those out to Junio:
http://mid.gmane.org/20160315015726.GA25295@xxxxxxxxxxxxx
The new TC 11/12 don't pass under cygwin.
Do we need cp932 ?
If not, we may use the paych from here:
https://github.com/tboegi/git/commit/379c01bf52464f8a50065b11af516127e9144045
Date: Tue Mar 15 05:03:18 2016 +0100
t9115: Use funcky file names that work under unicode FS
Don't use funky file names, that can not be created under
HFS or NTFS.
diff --git a/t/t9115-git-svn-dcommit-funky-renames.sh
b/t/t9115-git-svn-dcommit-funky-renames.sh
index 0990f8d..d022f0d 100755
--- a/t/t9115-git-svn-dcommit-funky-renames.sh
+++ b/t/t9115-git-svn-dcommit-funky-renames.sh
@@ -93,11 +93,11 @@ test_expect_success 'git svn rebase works inside a
fresh-cloned repository' '
# > to special UNICODE characters in the range 0xf000 to 0xf0ff (the
# > "Private use area") when creating or accessing files.
prepare_a_utf8_locale
-test_expect_success UTF8 'svn.pathnameencoding=cp932 new file on dcommit' '
+test_expect_success UTF8 'svn.pathnameencoding=ISO8859-1 new file on dcommit' '
LC_ALL=$a_utf8_locale &&
export LC_ALL &&
- neq=$(printf "\201\202") &&
- git config svn.pathnameencoding cp932 &&
+ neq=$(printf "\303\244") &&
+ git config svn.pathnameencoding ISO8859-1 &&
echo neq >"$neq" &&
git add "$neq" &&
git commit -m "neq" &&
@@ -105,11 +105,11 @@ 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 'svn.pathnameencoding=ISO8859-1 rename on dcommit' '
LC_ALL=$a_utf8_locale &&
export LC_ALL &&
- inf=$(printf "\201\207") &&
- git config svn.pathnameencoding cp932 &&
+ inf=$(printf "\303\226") &&
+ git config svn.pathnameencoding ISO8859-1 &&
echo inf >"$inf" &&
git add "$inf" &&
git commit -m "inf" &&
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html