diff options
author | https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 <https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4@web> | 2016-01-19 16:39:49 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2016-01-19 16:39:49 +0000 |
commit | ea966fdad036ea404a3e1a64c99e791bce396f43 (patch) | |
tree | 2f397982f47ffa40ffb07f858c458f4d0df062cf /doc/todo | |
parent | 4e8eec185906afc9ed8f060ec7464ee2711f8bc8 (diff) |
Added a comment
Diffstat (limited to 'doc/todo')
-rw-r--r-- | doc/todo/--batch_for_find/comment_2_9873396186f4d24088fd746f42373678._comment | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/doc/todo/--batch_for_find/comment_2_9873396186f4d24088fd746f42373678._comment b/doc/todo/--batch_for_find/comment_2_9873396186f4d24088fd746f42373678._comment new file mode 100644 index 000000000..416e588e1 --- /dev/null +++ b/doc/todo/--batch_for_find/comment_2_9873396186f4d24088fd746f42373678._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" + subject="comment 2" + date="2016-01-19T16:39:49Z" + content=""" +info -- nope, since it returns the same success and size = 0 bytes for a 0-length file which is under annex regardless either its precious load is present locally or not + +[[!format sh \"\"\" + +$> git annex find empty +$> git annex info --json empty +{\"command\":\"info empty\",\"file\":\"empty\",\"size\":\"0 bytes\",\"key\":\"SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\",\"success\":true} + +$> git annex get empty +get empty (from web...) +/tmp/123/.git/annex/tmp/SHA256E-s0--e3b0c44298fc1c149af [ <=> ] 0 --.-KB/s in 0s +(checksum...) ok +(recording state in git...) + +$> git annex info --json empty +{\"command\":\"info empty\",\"file\":\"empty\",\"size\":\"0 bytes\",\"key\":\"SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\",\"success\":true} + + +\"\"\"]] + +I could use whereis (--batch is TODO for it as well) and analyze output either any remote claims it to be \"here\" though. +"""]] |