mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

todo

Browse source
This commit is contained in:
Joey Hess 2025-03-12 12:11:39 -04:00
parent 0712ae020c
commit 21b45da406
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/todo/compute_special_remote_remaining_todos.mdwn
View file

@ -1,7 +1,12 @@
This is the remainder of my todo list while I was building the This is the remainder of my todo list while I was building the
compute special remote. --[[Joey]] compute special remote. --[[Joey]]
* write a tip showing how to use this * recompute should stage files in git. Otherwise,
`git-annex drop` after recompute --reproducible drops the staged
file, and `git-annex get` gets the staged file, and if it wasn't
actually reproducible, this is not apparent.
This is blocking adding the tip.
* Support parallel get of input files. The design allows for this, * Support parallel get of input files. The design allows for this,
but how much parallelism makes sense? Would it be possible to use the but how much parallelism makes sense? Would it be possible to use the
@ -10,7 +15,12 @@ compute special remote. --[[Joey]]
* compute on input files in submodules * compute on input files in submodules
* annex.diskreserve can be violated if getting a file computes it but also * annex.diskreserve can be violated if getting a file computes it but also
some other output files, which get added to the annex. some other output files, which get added to the annex. This can't be
avoided at addcomputed time, but when getting later from the compute
remote, it could check (but not when using VURL without size information)
* annex.diskreserve can also be violated if computing a file gets source
files that are larger than the disk reserve. This could be checked.
* would be nice to have a way to see what computations are used by a * would be nice to have a way to see what computations are used by a
compute remote for a file. Put it in `whereis` output? But it's not an compute remote for a file. Put it in `whereis` output? But it's not an