)]}'
{"doc/manpages/swift-container-reconciler.1":[{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"d4655dc4d42ddd57c3cba16383c215e51842f43d","unresolved":false,"context_lines":[{"line_number":31,"context_line":"queue similar to the object-expirer\u0027s queue."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Discovering that the object is in the wrong policy will be done in"},{"line_number":34,"context_line":"subsequent commits by the container replicator; this is the daemon"},{"line_number":35,"context_line":"that handles them once they happen."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Like the object expirer, you only need to run one of these per cluster"}],"source_content_type":"text/troff","patch_set":2,"id":"9a89bdaa_f51b40c8","line":34,"updated":"2016-09-06 22:34:09.000000000","message":"nit: \"subsequent commits\" is an odd choice of words here. Is this a holdover from a patch chain in gerrit, or is it more about referring to stuff that the container replicator will do?","commit_id":"0f761852f8aeca0081405323d1dc23ae08f35fc4"}]}