From c5c95ab08590be5c43c191abb7f44db976f568f9 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 10 Nov 2015 15:29:10 -0400 Subject: [PATCH] response --- ...ment_1_f4b439f7d9ce20d4b5dc8d728cb2e180._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__/comment_1_f4b439f7d9ce20d4b5dc8d728cb2e180._comment diff --git a/doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__/comment_1_f4b439f7d9ce20d4b5dc8d728cb2e180._comment b/doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__/comment_1_f4b439f7d9ce20d4b5dc8d728cb2e180._comment new file mode 100644 index 0000000000..a261a0dc01 --- /dev/null +++ b/doc/forum/How_does_git-annex_handle_rsyncing_between_different_OSes_with_regards_to_UTF-8__63__/comment_1_f4b439f7d9ce20d4b5dc8d728cb2e180._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-11-10T19:19:47Z" + content=""" +Both git and git-annex both treat filenames as strings of bytes, with no +particular encoding, to the extent supported by the OS[1]. This may result +in a checkout of git repository having filenames that don't display well on +a different system. + +[1] Of course any reasonable Unix treats filenames like that too.. but +Windows only supports unicode filenames. +"""]]