summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmMLeU-zCzx2mc5pL2XT8a1UNkQwHAHjg8 <daniele@web>2014-07-10 03:07:00 +0000
committerGravatar admin <admin@branchable.com>2014-07-10 03:07:00 +0000
commit6d04fff1469eefdcf6ec6963be4a9487ad318bc0 (patch)
tree00df150ca260cfc9c3de00db5242f735b1e7f946
parentedebaf6a5bc72ec91822822fa8432f0667a2268f (diff)
small change
-rw-r--r--doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn2
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn b/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn
index c78469238..e484c4f0e 100644
--- a/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn
+++ b/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn
@@ -30,6 +30,4 @@ The expected behavior here is that B gets the new file (or change) from box.com,
**What am I missing? Should I do something differently to get this behavior?**
-(This use-case is important for me because I need to keep some binary files in sync. These files are frequently modified by either *B* or *A*, and very often one of the two repos is not online. The different versions can't be simply merged back because of the binary nature of the files.)
-
Thanks everyone for your help.