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

update

Browse source
This commit is contained in:
Joey Hess 2025-03-06 12:52:12 -04:00
parent c6c6e2632d
commit 1e9bb30c4e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 13 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

13
TODO-compute
View file

@ -1,7 +1,8 @@
* 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
url. Maybe a separate command? That would also allow querying for eg, url. Maybe a separate command? That would also allow querying for eg,
what files are inputs for another file. what files are inputs for another file. Or it could be exposed in the
Remote interface, and made into a file matching option.
* "getting input from <file>" message uses the original filename, * "getting input from <file>" message uses the original filename,
but that file might have been renamed. Would be more clear to use but that file might have been renamed. Would be more clear to use
@ -16,6 +17,15 @@
* Perhaps recompute should write a new version of a file as an unlocked * Perhaps recompute should write a new version of a file as an unlocked
file when the file is currently unlocked? file when the file is currently unlocked?
Problem: Since recompute does not stage the file, it would have to write
the content to the working tree. And then the user would need to
git-annex add. But then, if the key was a VURL key, it would add it with
the default backend instead, and the file would no longer use a computed
key.
So it, seems that, for this to be done, recompute would need to stage the
pointer file.
* compute on files in submodules * compute on files in submodules
* recompute could ingest keys for other files than the one being * recompute could ingest keys for other files than the one being
@ -42,4 +52,3 @@
that recompute should also support recomputing non-annexed files. that recompute should also support recomputing non-annexed files.
Otherwise, adding a file and then recomputing it would vary in Otherwise, adding a file and then recomputing it would vary in
what the content of the file is, depending on annex.smallfiles setting. what the content of the file is, depending on annex.smallfiles setting.

4
doc/git-annex-recompute.mdwn
View file

@ -29,9 +29,9 @@ but is not staged, in order to avoid overwriting any staged changes.
Only recompute files that were computed by this compute remote. Only recompute files that were computed by this compute remote.
When this option is not used, all computed files are recomputed using When this option is not used, all computed files are recomputed using
whatever compute remote was originally used to add them. In cases where whatever compute remote was originally used to add them. (In cases where
a file can be computed by multiple remotes, the one with the lowest a file can be computed by multiple remotes, the one with the lowest
configured cost will be used. configured cost is used.)
* `--unreproducible`, `-u` * `--unreproducible`, `-u`