From 2dcfef4e455658df63d79bab9550d8462ed6ef7d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 14 Mar 2020 15:46:53 -0400 Subject: [PATCH] comment --- ...t_1_b1ac799adea59dad8fe148183060fb22._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/filenames_with_dots_and_spaces_can_not_be_exported/comment_1_b1ac799adea59dad8fe148183060fb22._comment diff --git a/doc/bugs/filenames_with_dots_and_spaces_can_not_be_exported/comment_1_b1ac799adea59dad8fe148183060fb22._comment b/doc/bugs/filenames_with_dots_and_spaces_can_not_be_exported/comment_1_b1ac799adea59dad8fe148183060fb22._comment new file mode 100644 index 0000000000..19da541f02 --- /dev/null +++ b/doc/bugs/filenames_with_dots_and_spaces_can_not_be_exported/comment_1_b1ac799adea59dad8fe148183060fb22._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-03-14T19:44:48Z" + content=""" +This seems likely to invole the specific filesystem used for +/media/thk/thk-sg2/. I woud not be surprised if eg FAT had limitations on +filenames with dots. + +Generally I think that if the remote being exported to cannot support the +filename, the export should fail. Mangling the filenames should be up to +the user. + +But there should certianly be a better error message than "failed" in this +case, so that at least needs to be fixed. +"""]]