comment
This commit is contained in:
parent
e414f2d1e6
commit
f6b2c21d52
1 changed files with 19 additions and 0 deletions
|
@ -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.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue