summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-12-07 15:45:08 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-12-07 15:45:08 -0400
commitad2339e17f69373e75aae5d1394de5d76d94c790 (patch)
treeffe51f9c236dadd340802c4604dcdd3fc190c9e9 /doc/todo
parentee0c34c8f2f94775b39ef10ed580cab47d2f929c (diff)
require "annex/objects/" before key in pointer files
This removes ambiguity, because while someone might have "WORM--foo" in a file that's not intended to be a git-annex pointer file, "annex/objects/WORM--foo" is less likely. Also, ee0c34c8f2f94775b39ef10ed580cab47d2f929c had a caveat about symlink targets being parsed as pointer files, and now the same parser is used for both. I did not include any hash directories before the key in the pointer file, as they're not needed. However, if they were included, the parser would still work ok.
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/smudge.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn
index 74a143580..eb8ce416b 100644
--- a/doc/todo/smudge.mdwn
+++ b/doc/todo/smudge.mdwn
@@ -158,7 +158,8 @@ Using git-annex on a crippled filesystem that does not support symlinks.
Data:
* An annex pointer file has as its first line the git-annex key
- that it's standing in for. Subsequent lines of the file might
+ that it's standing in for (prefixed with "annex/objects/", similar to
+ an annex symlink target). Subsequent lines of the file might
be a message saying that the file's content is not currently available.
An annex pointer file is checked into the git repository the same way
that an annex symlink is checked in.