)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":12279,"name":"Janie Richling","email":"jrichli@us.ibm.com","username":"jrichli"},"change_message_id":"a129118cfe666f4845179f6f982eb8040897ead3","unresolved":false,"context_lines":[{"line_number":20,"context_line":"received an update directly and therefore no hashes.invalid."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"When using sync_method \u003d ssync replication updates the hashes.invalid"},{"line_number":23,"context_line":"like any normal update to the partition and therefore all partitions"},{"line_number":24,"context_line":"always have a hashes.invalid."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"This change opts to ignores these implementation details in the probe"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"fa31d9ce_0952b367","line":23,"updated":"2017-02-10 21:48:26.000000000","message":"I still dont know the details of why ssync doesn\u0027t behave as described in the previous paragraph for rsync.  But that is just my ignorance, and i will seek to learn about that.\n\nI can follow the reasoning here, and it makes sense.","commit_id":"5bb3ea162c7cd264d0c434bc8ac8240f964d2904"}]}
