summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-03-05 16:53:34 +0000
committerGravatar admin <admin@branchable.com>2014-03-05 16:53:34 +0000
commit5903db00bd7d49d0163c580a92aa682b931d3943 (patch)
treeafd0d18ec03f1baeb9e42234d3f212bc2dc0a79f
parent3505227df9a6a9104ed303b99c38937a7cfe0213 (diff)
Added a comment
-rw-r--r--doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment b/doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment
new file mode 100644
index 000000000..923e1ccba
--- /dev/null
+++ b/doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 5"
+ date="2014-03-05T16:53:33Z"
+ content="""
+You have an older version of git, which does not support --no-dangling.
+
+git-annex will detect that, and omit the option. This does make it more likely that git fsck is outputing a ton of information, so I continue to think that's the most likely cause of the memory use.
+
+Please verify with: git fsck --no-reflogs |wc
+"""]]