diff options
| author |  spwhitton <spwhitton@web> | 2013-04-17 17:02:12 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-04-17 17:02:12 +0000 |
| commit | 4cba7244d64da57aa29aa2306fd4d76398231c07 (patch) | |
| tree | ec54a378eccb4170a9353fe191f1a1520cfff5d8 | |
| parent | 90f630b29163320765286add4fbf4f3a5eb34b40 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_4_02c32c2521ba1a1eaa19eaca7281f2a6._comment | 10 |
1 files changed, 10 insertions, 0 deletions
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 000000000..25d07e8ad --- /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. +"""]] |