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

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