summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-01-20 15:13:24 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-01-20 15:13:24 -0400
commit670173ef1001932cfe8401efbb27c9165a1241a6 (patch)
treeed9afe9fd4062a7a87f8e90d8c33c999ff8d24e9 /doc
parent9279fd6baf846d80249fef9e5a35a387cc5be713 (diff)
response
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/How_can_I_recover_from_misadventure__63__/comment_3_484fc154c68ba59939aae4452c663ce6._comment18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/How_can_I_recover_from_misadventure__63__/comment_3_484fc154c68ba59939aae4452c663ce6._comment b/doc/forum/How_can_I_recover_from_misadventure__63__/comment_3_484fc154c68ba59939aae4452c663ce6._comment
new file mode 100644
index 000000000..25732bb4b
--- /dev/null
+++ b/doc/forum/How_can_I_recover_from_misadventure__63__/comment_3_484fc154c68ba59939aae4452c663ce6._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-01-20T19:08:34Z"
+ content="""
+So, this seems to suggest that `git annex add` exited before it got around
+to checking all the files it had added into the git repository.
+
+I don't see how that could happen if the command exited successfully.
+If it were interrupted, sure.
+
+Normally I'd recommend that `git annex add` just be re-run to recover from
+an interrupted add. But if it's just going to exit for some reason again,
+I guess that won't work.
+
+I think you need to strace a git-annex command like `git-annex copy --to S3`
+and see if there's some clue why it's exiting unexpectedly.
+"""]]