diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-02-17 17:37:36 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-02-17 17:37:36 -0400 |
commit | 25be885632026b0c41cc2c513cf1fb437849512b (patch) | |
tree | a07c5ee14261040799ebfe3d1019808b4a9ae284 | |
parent | 4e2815a34f145f20b36160e6495363889c45f6cc (diff) |
wtf
-rw-r--r-- | doc/forum/What_happens_after_terminated_add_of_huge_picture_folder__63__/comment_3_f628f146a0c652f812c09f78bd574b77._comment | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/forum/What_happens_after_terminated_add_of_huge_picture_folder__63__/comment_3_f628f146a0c652f812c09f78bd574b77._comment b/doc/forum/What_happens_after_terminated_add_of_huge_picture_folder__63__/comment_3_f628f146a0c652f812c09f78bd574b77._comment new file mode 100644 index 000000000..b5814c7c7 --- /dev/null +++ b/doc/forum/What_happens_after_terminated_add_of_huge_picture_folder__63__/comment_3_f628f146a0c652f812c09f78bd574b77._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-02-17T21:31:42Z" + content=""" +There is never a reason to run "git reset --hard git-annex"! For that matter, +don't mess with the git-annex branch if you have not read and understand +the [[internals]] documentation. Even if you have, it's entirely the wrong +thing to be messing with in this situation. It has nothing at all to do +with your problem, except that after running that completely random reset +command, you now have two problems.. + +The right answer to your interrupted add is something like: + +* `git reset --hard master` +* Or, run the `git-annex add` command again and let it resume +* Or, run `git commit` to commit any changes the add made, + followed by `git annex unannex` to back out adding those files. + +Or, if this is an entirely new git repo that you have +never committed to before +(my guess based on the "bad default revision 'HEAD'"), +just `rm -rf .git` and start over. +"""]] |