)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"74fbf75fcc63a1eeb50ad6fad92ef9d2c12aea9e","unresolved":true,"context_lines":[{"line_number":12,"context_line":"the requirements repository branches."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Until the requirements repository has as stable/2023.1 branch, tests will"},{"line_number":15,"context_line":"continue to use the upper-constraints list on master."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Change-Id: I462ec85c0f856ef0cb05592b65b1d7bbc7de8a4e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"49b5db97_23d882c2","line":15,"updated":"2023-03-13 12:41:16.000000000","message":"This sounds weird, this patch is against exactly the mentioned branch. Is this just because this is a generic message for any branching repo? Is it still correct to apply this patch here or should there be a different one now?","commit_id":"65245016de7cf2d1e585eeb1378aac6aa6d75de0"}]}