diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-10-16 18:04:30 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-10-16 18:04:30 +0000 |
| commit | a564603bd1a8f4bb69c72ebcf2a2bd772863508f (patch) | |
| tree | 6e6ab6f2e133046696c9bf5cf002b2e0624852ee | |
| parent | a0dee21fbbe69f53a7427667ad5c4773ddca7e30 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment new file mode 100644 index 000000000..7df35b33d --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 2" + date="2013-10-16T18:04:27Z" + content=""" +I can confirm this bug, thanks for a good reproduction recipe. + +However, there is no actual data loss. If you switch to repo to indirect mode, you can use `git checkout` to check out the past versions from before the botched merge. When you do, you'll find that the files that the merge seemingly deleted in fact still have their contents present. It is preserved in `.git/annex/objects` by the automatic merge conflict resolution code, which does that whenever it deletes a file, whether for good reasons or for buggy reasons. + +So if you feel you lost data due to this, you can almost certainly get it back and I'm happy to help with that. + + +"""]] |