Recent comments posted to this site:

It would be awesome if there was the same --all option, and if the command produced something in bare repos, just like with the move / copy commands. At the moment for instance, it seems running git annex find on a bare repo returns nothing. There would be the question of the output format, but I guess one key per line is the obvious format one wants. I personally would want to run git annex find before a git annex move/copy, as a kind of dry-run, i.e. just to see the list of keys that will be transferred.
Comment by disteph Mon Oct 22 17:19:21 2018

You can use git annex findref master in a bare repository, which is like find but operates on some branch.

I am not convinced that find --all would really be that useful, since it would have to display keys and not filenames, and find is all about displaying filenames. I did make find error out in a bare repo rather than not doing anything.

Comment by joey Mon Oct 22 17:19:21 2018
wget https://git-annex.branchable.com/install/Android/git-annex-install.sh

This seems to download a html.

Comment by hoxu Mon Oct 22 17:19:21 2018
Comment by CandyAngel Mon Oct 22 17:19:21 2018

Thank you for reporting that, I have fixed the url.

I'd again like to ask that, if you have any kind of problem or bug with this Android build of git-annex, you open a bug report rather than posting a problem here.

Comment by joey Mon Oct 22 17:19:21 2018
What is the intended use case for CHECKURL-MULTI? Are there examples of external special remote implementations that use this response?
Comment by Ilya_Shlyakhter Mon Oct 22 17:19:21 2018

You can use git annex findref master in a bare repository, which is like find but operates on some branch.

I am not convinced that find --all would really be that useful, since it would have to display keys and not filenames, and find is all about displaying filenames. I did make find error out in a bare repo rather than not doing anything.

Thanks for the quick answer and for the tip. findref still displays file names, so OK, I can pipe the output with lookupkey to have the corresponding list of keys. Still, my understanding is that the computation is not the same as a potential find --all (or find on bare repos), in the sense that commands like move --all (or move on bare repos) only scan the files that are present in the repo, whereas git annex findref master looks at the whole branch regardless of where the files are. Sure, I can filter it with findref master --in=here, but the computational cost wouldn't be the same, would it? (imagining that my repo contains orders of magnitude fewer files than the branch) Also, move --all catches past versions of files that are still in the repo, i.e. "unused files", whereas I guess findref master --in=here would miss them? It's just that commands like move --all start by doing the job I want before taking an action on the files, so I just wish there was a "no-action" version of them. A --dry-run option in move and copy would be good enough. I tried to trick the move command with a move --all ... --from=here --to=here but of course I was outsmarted by the command :-)

Comment by disteph Mon Oct 22 17:19:21 2018
Does this require 4.x?
Comment by http://josh.easyid.net/ Sun Oct 14 00:20:01 2018
Availability in F-Droid would be really neat. I imagine the unusual build requirements would require some work though.
Comment by http://id.clacke.se/ Sun Oct 14 00:20:01 2018
Comment by http://lj.rossia.org/users/imz/ Sun Oct 14 00:20:01 2018