diff options
| -rw-r--r-- | doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_6_e71b251db2ff1f52a40fec40303cdefc._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_6_e71b251db2ff1f52a40fec40303cdefc._comment b/doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_6_e71b251db2ff1f52a40fec40303cdefc._comment new file mode 100644 index 000000000..3fcbf200b --- /dev/null +++ b/doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_6_e71b251db2ff1f52a40fec40303cdefc._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="zardoz" + ip="78.48.163.229" + subject="comment 6" + date="2014-08-22T13:15:06Z" + content=""" +I tried git annex repair on the repo (before doing any adds). It reports no fsck errors, but the repair then dies from a stack overflow. + +[[!format sh \"\"\" +Running git fsck ... +No problems found. +Stack space overflow: current size 8388608 bytes. +Use `+RTS -Ksize -RTS' to increase it. +\"\"\"]] +"""]] |