summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2022-04-11 13:52:21 +0300
committerFrederick Muriuki Muriithi2022-04-11 13:52:53 +0300
commita905038bafb977809d4f6cd4a9420760a8126f80 (patch)
treee9fb068d7d2ef8f857a5ba6f6a6a767d3bf001e7 /issues
parent0372522c5ba0382bc0e16b73aeb5771db2ec5887 (diff)
downloadgn-gemtext-a905038bafb977809d4f6cd4a9420760a8126f80.tar.gz
Add a question to the issue
Diffstat (limited to 'issues')
-rw-r--r--issues/rewrite-qc-and-qc-uploads-in-python.gmi10
1 files changed, 10 insertions, 0 deletions
diff --git a/issues/rewrite-qc-and-qc-uploads-in-python.gmi b/issues/rewrite-qc-and-qc-uploads-in-python.gmi
index 159ea30..cd7b0e0 100644
--- a/issues/rewrite-qc-and-qc-uploads-in-python.gmi
+++ b/issues/rewrite-qc-and-qc-uploads-in-python.gmi
@@ -63,3 +63,13 @@ The requirement
* check line endings to make sure they are Unix and not DOS
seems a little unnecessary if the files are not used for anything else. Most programming languages these days have facilities for translating the line endings appropriately, and so, we really should not add the manual cognitive overhead to the users, unless it is an absolute necessity, and even then, we will probably be doing something wrong. Is this requirement absolutely necessary?
+
+
+#### Question 03
+
+Can there be zero values, i.e.
+
+* "0.000", "00.000", ... etc. for average files
+* "0.000000, "00.00000000", ... etc. for standard error files
+
+in the files?