diff options
| author |  Alexander Foremny <aforemny@posteo.de> | 2023-10-16 23:34:06 +0200 |
|---|---|---|
| committer | Alexander Foremny <aforemny@posteo.de> | 2023-10-16 23:34:06 +0200 |
| commit | 7d96881886d375f9994d576751b063029fedf38e (patch) | |
| tree | ab3c74aabd53f3f00171c8767096b08a8b3717a7 /app/Main.hs | |
| parent | c8a54f5e47f9b8a317bd6bbe5cb4ab234f61c8b6 (diff) | |
comment add-command-for-regenerating-the-cache
Diffstat (limited to 'app/Main.hs')
| -rw-r--r-- | app/Main.hs | 11 |
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 -- |