aboutsummaryrefslogtreecommitdiffstats
path: root/app
diff options
context:
space:
mode:
Diffstat (limited to 'app')
-rw-r--r--app/Main.hs11
1 files changed, 11 insertions, 0 deletions
diff --git a/app/Main.hs b/app/Main.hs
index 516aeab..c3a50fc 100644
--- a/app/Main.hs
+++ b/app/Main.hs
@@ -362,6 +362,7 @@
--
-- @topic options
-- @topic cache
+-- @scheduled 2023-10-30
--
-- COMMENT What is the point of this command? Can't caches be handled
-- transparently to the user?
@@ -374,6 +375,16 @@
-- environment setup scripts. And then the first-commit option would
-- make it possible to use very old repostories without a too long
-- initial delay.
+--
+-- COMMENT The caching works *transparently* for the user if the user is not
+-- aware of the cache at all. If there are cache commands (or options), then it
+-- is not transparent.
+--
+-- I get that we want to limit provenance generation somewhat, and that will
+-- have to be solved in an intransparent manner.. but I am not fully
+-- understanding the proposal.
+--
+-- Maybe you could walk me through it in our next session?
-- TODO Add global option for specifying first considered commit
--