summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar zardoz <zardoz@web>2014-09-15 10:34:36 +0000
committerGravatar admin <admin@branchable.com>2014-09-15 10:34:36 +0000
commit8832968cbb459f970887f0b2febc260b56b82993 (patch)
treea2903df81a76ca9f4b73dd31d074c79b666e40df
parent6667f0e2404a57da299dfb743b6a258ce30c1f5a (diff)
Added a comment
-rw-r--r--doc/internals/comment_3_5a26ee5aab274f321a4ea6f8527f53bd._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/internals/comment_3_5a26ee5aab274f321a4ea6f8527f53bd._comment b/doc/internals/comment_3_5a26ee5aab274f321a4ea6f8527f53bd._comment
new file mode 100644
index 000000000..099f4c8ca
--- /dev/null
+++ b/doc/internals/comment_3_5a26ee5aab274f321a4ea6f8527f53bd._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="zardoz"
+ ip="134.147.14.84"
+ subject="comment 3"
+ date="2014-09-15T10:34:36Z"
+ content="""
+Some documentation that would be nice having added in the appropriate places:
+
+* Exactly how is the index file being used? Is this just a copy of the git index file that we would get when checking out the git-annex branch? Why is the file kept around? Which sort of operations are done on the index, e.g. when doing git annex add?
+
+* For all time-stamped data-structures: Exactly which significance does the time-stamp have? E.g., for uuid.log, is this the date the name was changed?
+"""]]