From 8c41f6a7ddb7f129e6ff4ccb29824207b98709c5 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg" Date: Sun, 13 Oct 2013 09:04:52 +0000 Subject: [PATCH] --- ...erge_upon_conflicting_directory-file_of_direct_repos.mdwn | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn index 245def940a..69364ae63b 100644 --- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn @@ -1,13 +1,16 @@ ### Please describe the problem. -Data loss due to incorrect merge of repos in direct mode. +Data loss due to incorrect merge of repos in direct mode. (I tested the same scenario in indirect mode and it worked fine there) Given 2 repos A and B, in direct mode: + 1. in A: mkdir f, with a file f in it 2. in B: touch f 3. in B: sync Result: Only an f.variant-f###remains, which is file f of B, and the merge conflict has already been automatically resolved. I.e. Directory f containing file f, is lost. +Expected result: remaining contents: f.variant-AAA which is file f of B, f.variant-BBB which is directory f of A, containing a file f. Merge conflict marked resolved. + ### What steps will reproduce the problem? Execute the script given below in additional information.