diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-03-27 14:01:33 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-03-27 14:01:33 -0400 |
| commit | 6a388d5a0b4070ae861f3dc822a31a8992a15341 (patch) | |
| tree | 52c5a04d5b0fd310ecff4c65e9d72db34d2ad694 | |
| parent | e9008d8159122957e6686b97d4f6ca5b360a1c39 (diff) | |
comment
| -rw-r--r-- | doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment new file mode 100644 index 000000000..dcedee1e6 --- /dev/null +++ b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-03-27T17:55:13Z" + content=""" +The intent in providing DIRHASH is to let external special remotes that +would like to do some hashing in their own backend storage get a value +that's suitable for that. + +I guess you're instead trying to use it to let the external special remote +access data stored in .git/annex/objects in the local repositpry. +And DIRHASH won't work for that; it's not even the right hash method. +(Not to mention, in direct mode, the data may not be stored in +.git/annex/objects at all.) + +If that's what you're looking for, I think that a new plumbing command +would be best. Something like `git annex contentlocation $KEY` outputting +a path to the content. +"""]] |