jianglai 440b06658d Add MOE equivalency for 2017-12-01 sync ... There has been quite some descriptiveness between github and our internal build. I had to manually push a commit (1c1f95992a) to bring github up-to-date. Now the github version is identical to what we'd get from doing a -dr-mkfoss. Hopefully the next time things will go smoothly. The culprit turns out to be MOE itself. It was not attributing changes to commits correctly when the change involves moving files as a result of modifications made to moe_config.json. When moe_config.json is altered in a CL to move files around, MOE always thinks that move happens in the first commit to be pushed. For example, if we have CL1,CL2,CL3, which correspond to CM1, CM2 and CM3 to be pushed to github, and a change to moe_config.json in CL3 moves a folder, MOE will think that move happens in CM1. This usually is not a problem when all commits are pushed, but when doing manual rebasing and cherry-picking, this will result in unintended dropped changes along with a commit. I'll do a push to github early next week to confirm that things are back to normal. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=177844920		2017-12-13 12:43:45 -05:00
..
registry	Add MOE equivalency for 2017-12-01 sync	2017-12-13 12:43:45 -05:00