diff options
author | Joey Hess <joeyh@joeyh.name> | 2016-10-10 15:03:27 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2016-10-10 15:03:27 -0400 |
commit | 5d85a812205db3cbfb23ce47a38f35e773d299d8 (patch) | |
tree | 44fbbeae85392e327c50588b889d7fd47fd2ca26 | |
parent | 661c79f7d0175a017e8f345b09ae13ebdfbf9022 (diff) |
devblog
-rw-r--r-- | doc/devblog/day_420__delayed_debugging.mdwn | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/devblog/day_420__delayed_debugging.mdwn b/doc/devblog/day_420__delayed_debugging.mdwn new file mode 100644 index 000000000..50c42965e --- /dev/null +++ b/doc/devblog/day_420__delayed_debugging.mdwn @@ -0,0 +1,17 @@ +Over a month ago, I had some reports that syncing into adjusted branches +was losing some files that had been committed. I couldn't reproduce it, but +IIRC both felix and tbm reported problems in this area. And, felix kindly +sent me enough of his git repo to hopefully reproduce it the problem. + +Finally got back to that today. Luckily, I *was* able to reproduce the bug +using felix's repo. The bug only occurs when there's a change deep in a +tree of an adjusted branch, and not always then. After staring at it for a +couple of hours, I finally found the problem; a modification flag was not +getting propigated in this case, and some changes made deep in the tree +were not getting included into parent trees. + +So, I think I've fixed it, but need to look at it some more to be sure, and +develop a test case. And fixing that exposed another bug in the same code. +Gotta run unfortunately, so will finish this tomorrow.. + +Today's work was sponsored by Riku Voipio. |