summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar mike.dacre@06f2e98956fc551180a694c61abd45921cd7369b <mikedacre@web>2015-06-30 00:49:51 +0000
committerGravatar admin <admin@branchable.com>2015-06-30 00:49:51 +0000
commit10cb30f834e92515d17e49bec9556586adf838bb (patch)
tree6d2c28195c8139de67abbbc1e7756305527a7a56
parent7acae66a27e9f51a4e5a40987a161bd41b87b050 (diff)
-rw-r--r--doc/forum/Restoring_files__63__.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/Restoring_files__63__.mdwn b/doc/forum/Restoring_files__63__.mdwn
new file mode 100644
index 000000000..d0bf86d90
--- /dev/null
+++ b/doc/forum/Restoring_files__63__.mdwn
@@ -0,0 +1,11 @@
+One of my users created a git annex repository a while ago and has since left the lab, and I think they messed it up badly.
+
+It looks like all of the data is present in the annex directory, but there are no files in main directory, other than the .git folder. The master branch seems to be gone, and the only branch left is called git-annex.
+
+git log gives the error "fatal: bad default revision 'HEAD'" when I first do git log, because the branch that I am on doesn't exist (the master branch). Changing to the git-annex branch works, but then I can't go back to the master branch because it doesn't exist.
+
+git annex unannex doesn't seem to do anything. Is there any way to get the data back following this kind of mess up?
+
+Thanks for your help
+
+-Mike