From 925648c297e407756c80016b1c8288e35552cf3e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 5 May 2022 10:57:17 -0400 Subject: [PATCH] comment --- ..._dbcdb6ae6fb1d06f4d5cf27cba4c69be._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/mimeencoding_detection_is_not_working/comment_1_dbcdb6ae6fb1d06f4d5cf27cba4c69be._comment diff --git a/doc/bugs/mimeencoding_detection_is_not_working/comment_1_dbcdb6ae6fb1d06f4d5cf27cba4c69be._comment b/doc/bugs/mimeencoding_detection_is_not_working/comment_1_dbcdb6ae6fb1d06f4d5cf27cba4c69be._comment new file mode 100644 index 0000000000..68257631cd --- /dev/null +++ b/doc/bugs/mimeencoding_detection_is_not_working/comment_1_dbcdb6ae6fb1d06f4d5cf27cba4c69be._comment @@ -0,0 +1,20 @@ +[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-05-05T14:50:13Z" + content=""" +Is your git-annex built with support for mime type +detection? Post the output of `git-annex version` + +I don't think it's possible that a filename can affect this. +I'd only believe that if you showed me the same content in a file without a +cryllic filename being treated differently. + +Also, when I try feeding all the data into `git-annex matchexpression`, +it behaves as expected: + + joey@darkstar:~/lib/tmp> if git-annex matchexpression --file=привет.jpg --size=100 --mimeencoding=binary --largefiles 'mimeencoding=binary and largerthan=0'; then echo match; fi + match + +You could try the same command to see if your git-annex behaves differently. +"""]]