From 31a4e449411e0c71e59bb81b65b99e0ac2dc75da Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlScsufvQF7s8TVTwPd-h_QiP5Hn_i-hrs" Date: Thu, 17 Jul 2014 15:29:59 +0000 Subject: [PATCH] --- ..._--maxdepth_option_for_git_annex_find.mdwn | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn diff --git a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn new file mode 100644 index 0000000000..f5a358aae0 --- /dev/null +++ b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn @@ -0,0 +1,24 @@ +`git annex find` currently makes for a great way to find which files are already local, and don't need to get `git annex get` gotten; obviously `ls` just shows me all the files in a given directory, disregarding git-annex (and without recursing to subdirectories). I think that adding a '--maxdepth' option to `git annex find` would make it much easier to use at directories high up in the directory structure, since currently `git annex find` recurses all subdirectories necessarily, when I really just want to see whether or not there are git-annex files present from a given directory. + +Obviously, since directories themselves are not git-annex objects, there is no way to say whether or not they are "present", but perhaps the most intuitive would be to say whether or not any git-annex files under a given directory are present. + +For example, if I have: +``` +./ ++-- subdir0/ +| +-- file0 (present in local git-annex repo) +| +-- file1 (present in local git-annex repo) ++-- subdir1/ +| +-- file0 (not present in local git-annex repo) +| +-- file1 (not present in local git-annex repo) ++-- file2 (present in local git-annex repo) +``` + +and I type `git annex find --maxdepth 1 .`, the output might look something like: +subdir0/ +file2 + +rather than: +subdir0/file0 +subdir0/file1 +file2