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

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