From 6bc2419f0286c4ac3fcb762bda4d45804489124d Mon Sep 17 00:00:00 2001 From: zardoz Date: Fri, 22 Aug 2014 18:57:37 +0000 Subject: [PATCH] Added a comment --- .../comment_8_f951981f0bf8cbaecfc46e7b9c903d70._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_8_f951981f0bf8cbaecfc46e7b9c903d70._comment diff --git a/doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_8_f951981f0bf8cbaecfc46e7b9c903d70._comment b/doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_8_f951981f0bf8cbaecfc46e7b9c903d70._comment new file mode 100644 index 0000000000..ec876d2ea4 --- /dev/null +++ b/doc/bugs/__34__error:_invalid_object__34____44___after_add__59___cannot_commit/comment_8_f951981f0bf8cbaecfc46e7b9c903d70._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="zardoz" + ip="78.48.163.229" + subject="comment 8" + date="2014-08-22T18:57:37Z" + content=""" +I just checked my other large git annex repo and noticed that here too I could no longer add files to the annex. The same observations as above apply. Here too on the tip of the git-anenx branch I had one huge commit in which I dropped the last of the unused WORM keys from another remote. Resetting the git-annex branch to git-annex~1 allowed me to make additions again, even though the reset tip was subsequently merged in again from the remote tracking branch. +"""]]