Gate a readme ending in a colon like a disk path

trust-scan-config passed any readme holding a colon as a tracked file,
while the parser takes one only when a path follows the colon, so a
scanned repository could still name a file on disk outside itself. The
two now share one test.

1 file changed, 7 insertions, 0 deletions

diff --git a/source/shared.c b/source/shared.cindex befd3e5..6e69666 100644--- a/source/shared.c+++ b/source/shared.c@@ -739,3 +739,10 @@ char *cgit_get_mimetype_for_filename(const char *filename) 	fclose(file); 	return NULL; }++int cgit_readme_is_tracked(const char *readme)+{+	const char *colon = strchr(readme, ':');++	return colon && colon[1];+}
diff --git a/source/shared.c b/source/shared.c
index befd3e5..6e69666 100644
--- a/source/shared.c
+++ b/source/shared.c
@@ -739,3 +739,10 @@ char *cgit_get_mimetype_for_filename(const char *filename)
 	fclose(file);
 	return NULL;
 }
+
+int cgit_readme_is_tracked(const char *readme)
+{
+	const char *colon = strchr(readme, ':');
+
+	return colon && colon[1];
+}