From 16702cd60871d294c8334200a83b753b0573ce47 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlScsufvQF7s8TVTwPd-h_QiP5Hn_i-hrs" Date: Mon, 21 Jul 2014 19:22:30 +0000 Subject: Added a comment: good point --- .../comment_4_c766c1465407324fc933db78be325b33._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/wishlist:_--maxdepth_option_for_git_annex_find/comment_4_c766c1465407324fc933db78be325b33._comment (limited to 'doc/todo/wishlist:_--maxdepth_option_for_git_annex_find') diff --git a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find/comment_4_c766c1465407324fc933db78be325b33._comment b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find/comment_4_c766c1465407324fc933db78be325b33._comment new file mode 100644 index 000000000..6025101e2 --- /dev/null +++ b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find/comment_4_c766c1465407324fc933db78be325b33._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlScsufvQF7s8TVTwPd-h_QiP5Hn_i-hrs" + nickname="Jason" + subject="good point" + date="2014-07-21T19:22:30Z" + content=""" +You make another good point `--maxdepth` is vague in this context... +I guess if we were to decide to come up with a summary option, it will have be named something else, like `--summary-depth`, where the default would be to represent all files of whatever depth, and specifying the option would take the output that would otherwise get from `git annex find `, truncate the paths to a certain depth, and then make a set thereof (to remove the many dups), that way any directory that had any files that would have been output by `git annex find `, that would also be at or above a certain depth, would be listed. + +I think if I get a chance I'll try to implement something like this. + +"""]] -- cgit v1.2.3