summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar clacke <clacke@web>2015-05-22 21:08:26 +0000
committerGravatar admin <admin@branchable.com>2015-05-22 21:08:26 +0000
commit88f2574f4135ad82e6c3064daf5b074a3e6ae6fb (patch)
tree83ab34c879e2d27dfff8527edf9e0537c0af102b
parent0c2026f3d4109e810b050090b44bb406b6a11954 (diff)
Added a comment
-rw-r--r--doc/bugs/rsync:_protocol_version_mismatch/comment_2_531b85c911d390b1b93ee55a8cf5d47e._comment11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/rsync:_protocol_version_mismatch/comment_2_531b85c911d390b1b93ee55a8cf5d47e._comment b/doc/bugs/rsync:_protocol_version_mismatch/comment_2_531b85c911d390b1b93ee55a8cf5d47e._comment
new file mode 100644
index 000000000..268f36993
--- /dev/null
+++ b/doc/bugs/rsync:_protocol_version_mismatch/comment_2_531b85c911d390b1b93ee55a8cf5d47e._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="clacke"
+ subject="comment 2"
+ date="2015-05-22T21:08:26Z"
+ content="""
+It's weirder than that. I add a cow union mount over it, it works fine.
+
+I copy the file, I drop the file, I remove the union mount. Again it's back in the broken state. Rebooting does not help, so it's not some very insistent lock.
+
+Next I will try a copy of the repo, to see if that is able to carry over whatever strange state this thing is in.
+"""]]