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

Added a comment

Browse source
This commit is contained in:
Dan 2022-07-29 22:02:56 +00:00 • committed by admin
parent 29f6b19525
commit e832676d38
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/git-annex-find/comment_14_2acf9c8a2d261ee69f3649b05581be4d._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="Dan"
avatar="http://cdn.libravatar.org/avatar/986de9e060699ae70ff7c31342393adc"
subject="comment 14"
date="2022-07-29T22:02:56Z"
content="""
Ah, I hadn't considered the parallel to the standard `find` command, but now that you mention that I understand where you're coming from and can appreciate why `whereis` is free of this association.
Still, I would think that a user who, after looking at the docs for `git annex find`, specified `--all` because they wanted to operate on keys would not be surprised.
I notice that the man page for `git annex find` already has a \"SEE ALSO\" reference to `git annex whereis`.
Could this be expanded so that it more clearly and prominently advises the reader who is looking to query against all known keys to check out the `--all` argument to `git annex whereis` as well as its `--format=` option if \"whereis\" information is not actually of interest?
"""]]