From f7a562bdc4ab2aa718aadc50e5386866cf4971c6 Mon Sep 17 00:00:00 2001 From: spwhitton Date: Wed, 17 Apr 2013 17:02:12 +0000 Subject: [PATCH] Added a comment --- ...comment_4_02c32c2521ba1a1eaa19eaca7281f2a6._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_4_02c32c2521ba1a1eaa19eaca7281f2a6._comment diff --git a/doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_4_02c32c2521ba1a1eaa19eaca7281f2a6._comment b/doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_4_02c32c2521ba1a1eaa19eaca7281f2a6._comment new file mode 100644 index 0000000000..25d07e8ad3 --- /dev/null +++ b/doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_4_02c32c2521ba1a1eaa19eaca7281f2a6._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="spwhitton" + ip="163.1.167.50" + subject="comment 4" + date="2013-04-17T17:02:11Z" + content=""" +I didn't think that git would let corruption spread either, but it did: the repository m3 which I showed a push to in my original post showed a broken refs/heads/git-annex too. You can see it happening when git tries to repack m3 after pushing to it in my original post. + +I am pretty sure that my HDD on the machine where this first occurred needs replacing; I've marked the remote as untrusted. +"""]]