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

fix up comment

Browse source
This commit is contained in:
Dan Kessler 2022-07-27 19:26:10 -04:00
parent f79cd648de
commit 2f0620a917
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/git-annex-find/comment_9_d7ea718f3a898bf9f3e1514802b99fec._comment
View file

@ -10,14 +10,17 @@ At first glance, it seems like the appropriate way to do this is with `git annex
Since I have recently `git annex sync`-ed, this doesn't turn up anything.
However, if I understand everything correctly, this *only* checks files that are reachable from my current working tree.
Thus, if there are a bunch of files in my (not currently checked out) `dev` branch that are *not* in my corktree, then this query will not discover them.
Thus, if there are a bunch of files in my (not currently checked out) `dev` branch that are *not* in my worktree, then this query will not discover them.
I can get them to be considered with `git annex find --in here --not --copies=2 --branch dev`.
I could manually (or script) a loop over all of my branches and repeat `git annex find --in here --not --copies=2 --branch ${branch}` to check all of my branches.
I could manually (or via script) loop over all of my branches and repeat `git annex find --in here --not --copies=2 --branch ${branch}` to check all of my branches.
However, this will only check the tips.
Suppose there's a file that previously existed (solely) in my master branch, but at some point it was `git rm`-ed. Then unless I specify using `--branch` a TREEISH that has that file, it will not be considered.
As a result, it seems like the safest thing for me to do is to instead run `git annex whereis --all --in here --not --copies=2` in order to identify keys corresponding to files that are (a) locally available but where (b) the number of copies is not 2 or greater (i.e., it is here and only here).
So, I need to use some sort of query tool that supports both the `--all` flag as well as all of the matching options.
The only thing I was able to find was `whereis`, so I can run `git annex whereis --all --in here --not --copies=2` in order to identify keys corresponding to files that are (a) locally available but where (b) the number of copies is not 2 or greater (i.e., it is here and only here).
I suppose I could also just plunge ahead with `git annex copy --to ${remote} --all --in here --not --copies=2`, but it's reassuring to be able to run the query and see what would need to get moved (as well as to see the query come back empty before I wipe the hard drive).
Is this an appropriate use of `git annex whereis`, or is there a way that I can use `git annex find` to accomplish this? I see discussion above regarding the lack of `--all` support for `git annex find` Perhaps this is all a roundabout way of asking that `--all` be supported in `git annex find`
Is this an appropriate use of `git annex whereis`, or is there a way that I can use `git annex find` to accomplish this, or perhaps some other query tool?
In essence, I just want a way of querying "all" of the objects that git annex has ever known about using all of the standard matching options.
I see discussion above regarding the lack of `--all` support for `git annex find`, which at the time suggested using `findref` instead but it seems like that has been deprecated in favor of `find`.
"""]]