)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"c7270b49f1ebcdbd59e438e50083879225da755b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c0675071_15977856","updated":"2024-01-24 07:01:58.000000000","message":"Don\u0027t we have merge conflicts in this patch? Same as in 2023.2 one.","commit_id":"60c4a0bf943198eee246dd1ab04f85de850993ff"},{"author":{"_account_id":34271,"name":"Miro Tomaska","display_name":"Miro Tomaska","email":"mtomaska@redhat.com","username":"mtomaska"},"change_message_id":"140b31f808d22b36d3fd5060b8b081897b4f3f61","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fb68d360_cb8d296b","in_reply_to":"c0675071_15977856","updated":"2024-01-24 15:57:25.000000000","message":"No. I see that cherry pick commit is listed as master but I cherry picked from the 2023.2. That is why I dropped the conflict section since the merge was clean. Let me update the commit message to list the 2023.2 patch. thank you for pointing that out","commit_id":"60c4a0bf943198eee246dd1ab04f85de850993ff"}]}
