From 292f3a42734a80bef045f008285ae0e1973c9079 Mon Sep 17 00:00:00 2001 From: ericm Date: Fri, 5 Oct 2018 10:58:40 +0000 Subject: [PATCH] --- ...ent_to_a_repo_that_only_wants_content_already_present.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/forum/Copy_modified_content_to_a_repo_that_only_wants_content_already_present.mdwn b/doc/forum/Copy_modified_content_to_a_repo_that_only_wants_content_already_present.mdwn index 26eb1e0e43..a5500d0b1b 100644 --- a/doc/forum/Copy_modified_content_to_a_repo_that_only_wants_content_already_present.mdwn +++ b/doc/forum/Copy_modified_content_to_a_repo_that_only_wants_content_already_present.mdwn @@ -5,8 +5,8 @@ I want the 2 client repos to only want content that is already present in the re And let's say the 2 client repos already contain the file **test.txt**. -When I modify test.txt in the laptop repo and run git `annex sync --content`, then go to the desktop repo and run `git annex sync`,
-the behavior I'm expecting is that **test.txt** in the desktop repo will be updated when sync is run since clients want content that is already present. +When I modify **test.txt** in the laptop repo and run `git annex sync --content`, then go to the desktop repo and run `git annex sync`,
+the behavior I'm expecting is that test.txt in the desktop repo will be updated when sync is run since clients want content that is already present. However, what happens is that the file **test.txt** in the desktop repo is **dropped**.
Is this the expected behavior when using `present` in the preferred content expression?