summaryrefslogtreecommitdiff
path: root/doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_pr...
diff options
context:
space:
mode:
authorGravatar https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 <https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4@web>2016-07-28 19:10:04 +0000
committerGravatar admin <admin@branchable.com>2016-07-28 19:10:04 +0000
commitec7dff0b2586c4a4ea1dc4091e5f891ddec60da8 (patch)
tree0266a8d2dd9c42cec60574cce2b46bed52e4f574 /doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_present.mdwn
parent9d43f493be415759c481f2b16dd95fafd066ebbb (diff)
Diffstat (limited to 'doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_present.mdwn')
-rw-r--r--doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_present.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_present.mdwn b/doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_present.mdwn
new file mode 100644
index 000000000..05737f621
--- /dev/null
+++ b/doc/todo/__39__info_filename__39___to_provide_information_either_content_is_locally_present.mdwn
@@ -0,0 +1 @@
+ATM in DataLad we rely on 'git annex find' to determine either files have content locally. Even though it could be used in a batch mode, I wondered if we could may be just use 'annex info' to obtain information either a file (or a key) has content locally? Another benefit would be is that within single command output we could determine also if a file under annex or not (instead of first doing e.g. 'info' to figure out if under annex and then 'find' again to figure out if content is present locally)