update in response to comment
This commit is contained in:
parent
fedee03654
commit
9e847d4786
2 changed files with 11 additions and 2 deletions
|
@ -291,14 +291,14 @@ handling a request.
|
|||
tracking the size of the file as it grows.)
|
||||
(git-annex does not send a reply to this message.)
|
||||
* `DIRHASH Key`
|
||||
Gets a two level hash associated with a Key. Something like "aB/Cd".
|
||||
Gets a two level hash associated with a Key. Something like "aB/Cd/".
|
||||
This is always the same for any given Key, so can be used for eg,
|
||||
creating hash directory structures to store Keys in. This is the same
|
||||
directory hash that git-annex uses inside `.git/annex/objects/`
|
||||
(git-annex replies with VALUE followed by the value.)
|
||||
* `DIRHASH-LOWER Key`
|
||||
Gets a two level hash associated with a Key, using only lower-case.
|
||||
Something like "abc/def".
|
||||
Something like "abc/def/".
|
||||
This is always the same for any given Key, so can be used for eg,
|
||||
creating hash directory structures to store Keys in. This is the same
|
||||
directory hash that is used by eg, the directory special remote.
|
||||
|
|
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""Re: DIRHASH ending in slash?"""
|
||||
date="2022-09-30T17:31:25Z"
|
||||
content="""
|
||||
Hmm, so it does. This would not have been my choice for ideal behavior, but
|
||||
I don't want to break things that depend on it now.
|
||||
So I've updated the documentation.
|
||||
"""]]
|
Loading…
Reference in a new issue