From 14897ec8e2153f2e81f5948ff42804e2a46a6762 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 20 Dec 2019 16:11:21 -0400 Subject: [PATCH] comment --- ..._08448687578634b6281ea285f18d87e7._comment | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/be_robust_to_additions_of_more_specific_mime_types_to_libmagic___40__e.g._application__47__json__41__/comment_2_08448687578634b6281ea285f18d87e7._comment diff --git a/doc/bugs/be_robust_to_additions_of_more_specific_mime_types_to_libmagic___40__e.g._application__47__json__41__/comment_2_08448687578634b6281ea285f18d87e7._comment b/doc/bugs/be_robust_to_additions_of_more_specific_mime_types_to_libmagic___40__e.g._application__47__json__41__/comment_2_08448687578634b6281ea285f18d87e7._comment new file mode 100644 index 0000000000..0cde6c7a1b --- /dev/null +++ b/doc/bugs/be_robust_to_additions_of_more_specific_mime_types_to_libmagic___40__e.g._application__47__json__41__/comment_2_08448687578634b6281ea285f18d87e7._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2019-12-20T20:00:14Z" + content=""" +Yes, mimeencoding=binary is intended for those cases where you just want a +robust (presumably) text/binary division. + +The "any mimetype matches" approach seems like it could break things too. +Consider: + + (not mimetype=text/plain and (mimetype=text/* or mimetype=application/json)) or mimetype=AI/buggy + +Currently a shell script is found to be only text/x-shellscript, +so it would match the above. If git-annex were changed to consider +all reported mime types, the shell script, being also text/plain +would not match. + +And then, once the mime database solves the halting problem and helpfully +starts flagging shell scripts as AI/buggy (all shell scripts are presumably +buggy so maybe that AI has an easy job), the behavior on the above example +would change for a third time, back to matching. +"""]]