Blame SOURCES/0031-Fix-question-mark-wildcard-withing-a-file-name.patch

f22e83
From 0da42468ac9518a544aad57d22d7697d6bdfa969 Mon Sep 17 00:00:00 2001
f22e83
From: Martin Sehnoutka <msehnout@redhat.com>
f22e83
Date: Thu, 17 Nov 2016 13:25:12 +0100
f22e83
Subject: [PATCH 31/59] Fix question mark wildcard withing a file name.
f22e83
f22e83
Previously '?' worked only at the end of a file name, now it can
f22e83
be used anywhere.
f22e83
---
f22e83
 ls.c | 3 ++-
f22e83
 1 file changed, 2 insertions(+), 1 deletion(-)
f22e83
f22e83
diff --git a/ls.c b/ls.c
f22e83
index 3c0988c..35c15c7 100644
f22e83
--- a/ls.c
f22e83
+++ b/ls.c
f22e83
@@ -459,7 +459,8 @@ vsf_filename_passes_filter(const struct mystr* p_filename_str,
f22e83
         must_match_at_current_pos = 0;
f22e83
       }
f22e83
     } while (locate_result.found &&
f22e83
-             str_getlen(&name_remain_str) > 0 && last_token != '*');
f22e83
+             str_getlen(&name_remain_str) > 0 &&
f22e83
+             last_token != '*' && last_token != '?');
f22e83
   }
f22e83
   /* Any incoming string left means no match unless we ended on the correct
f22e83
    * type of wildcard.
f22e83
-- 
f22e83
2.14.4
f22e83