aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2021-08-27 21:12:56 -0300
committerEuAndreh <eu@euandre.org>2021-08-27 21:12:56 -0300
commitd9ab1762ae00ce21beb2c43b97b40e31e9b2c4d6 (patch)
tree31807e9fd51ae0a6d0b9946f3ce083405c60a1f0
parentTODOs.md: Add links to zlib implementations on Resources section (diff)
downloadgistatic-d9ab1762ae00ce21beb2c43b97b40e31e9b2c4d6.tar.gz
gistatic-d9ab1762ae00ce21beb2c43b97b40e31e9b2c4d6.tar.xz
TODOs.md: Add comments to the body of #task-a6bdaeb0-7099-c728-2b7c-b080aa2fba33
-rw-r--r--TODOs.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/TODOs.md b/TODOs.md
index e6bd403..fc149f9 100644
--- a/TODOs.md
+++ b/TODOs.md
@@ -155,6 +155,22 @@ Links I found useful:
[clang-tidy]: https://clang.llvm.org/extra/clang-tidy/
[Milu]: https://github.com/yuejia/Milu
+When using accumulating the test corpus, how to maintain it?
+Is this something one would erase from time to time?
+Or is this something that could and should be kept alonside the fuzz targets
+themselves?
+If they are to be kept, how to manage them?
+Make periodic tarballs and put them on a server somewhere?
+After all, commiting this data is completly undesirable.
+Maybe creating periodic tarballs, make torrent files for those and commit the
+torrent files themselves.
+By also creating some simple tooling to keep old tarballs versions around on my
+machine and on a web server (to serve as a "web seed"), than this effectively
+allows sharing of the corpus.
+By also creating some simple tooling to keep old tarballs versions around on my
+machine and on a web server (to serve as a "web seed"), than this effectively
+allows sharing of the corpus.
+
## DONE Embed `src/unit-test.{c,h}` into `src/gistatic.c` {#task-ae96e5b6-ab04-3a3d-1777-b28031273a19}
- DONE in 2021-07-31