diff options
| author |  http://joeyh.name/ <joey@web> | 2013-04-08 17:23:24 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-04-08 17:23:24 +0000 |
| commit | dd67b158a60fb20671a3ecc32f7b7d75b543ee8b (patch) | |
| tree | 781b6e11563042f5343e0ae10a8eef194a00eb71 | |
| parent | f9deff84b3a5cdc5766adf964c78732626e1387e (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_3_3523884833b5fd458a35f898797bf897._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_3_3523884833b5fd458a35f898797bf897._comment b/doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_3_3523884833b5fd458a35f898797bf897._comment new file mode 100644 index 000000000..21511d2ec --- /dev/null +++ b/doc/forum/__34__unable_to_resolve_reference_refs__47__heads__47__git-annex__34__/comment_3_3523884833b5fd458a35f898797bf897._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 3" + date="2013-04-08T17:23:24Z" + content=""" +1. I don't understand how corruption could spread between git repositories. git is supposed to use checksums to prevent bad data propigating. I would be running a lot of `git fsck` if I were you. Yes, `git annex fsck` will update location log information for files it finds in the local repository. + +2. Again this looks like something is corrupting your repository when git writes it. Perhaps bad memory? I think you need to get to the root of the problem with the corrupting git repositories. +"""]] |