)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":35099,"name":"Jakub Jelinek","email":"jakub.jelinek@cern.ch","username":"kubajj"},"change_message_id":"6423b2cad50b10d872eec72ed60b4851133bb9a4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"5710353a_4c4cd300","updated":"2025-01-16 09:35:16.000000000","message":"Ok, that\u0027s probably better","commit_id":"2ece938671b60d2bee0f55120035afb8c4f2bbb4"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"8907ce3a006685c3fc87fa66c1a8982988f8c35b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"aa343019_c6d62475","updated":"2025-01-17 19:33:35.000000000","message":"On your first backport, I\u0027d suggest merging the release note patch and actual patch into one","commit_id":"2ece938671b60d2bee0f55120035afb8c4f2bbb4"},{"author":{"_account_id":23851,"name":"Riccardo Pittau","email":"elfosardo@gmail.com","username":"elfosardo"},"change_message_id":"6d99e388256fd442f0a81ce8da4a734e776dfe66","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"2c9d3f82_3af83f5f","updated":"2025-01-16 09:41:09.000000000","message":"thanks","commit_id":"2ece938671b60d2bee0f55120035afb8c4f2bbb4"}],"releasenotes/notes/fix-raid-volume-name-ac9013e7b5cf3d46.yaml":[{"author":{"_account_id":23851,"name":"Riccardo Pittau","email":"elfosardo@gmail.com","username":"elfosardo"},"change_message_id":"98fd74a5786e6741f1bc66563a99dd2a0cd38819","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The fix for the bug 2073406 - Incorrect name assigned to software raid device."},{"line_number":5,"context_line":"    The use of md_device as the default volume name if the volume name of a RAID"},{"line_number":6,"context_line":"    array hasn\u0027t been specified caused a \u0027Not POSIX compatible\u0027 error."},{"line_number":7,"context_line":"    This has been fixed by using just the last part of the md_device."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"94ef5890_94696aa3","line":4,"updated":"2025-01-16 09:31:30.000000000","message":"I would remove this line, if you want add a link to the launchpad issue at the end","commit_id":"441be20683e41f6eb7f89a245731a815d4389397"},{"author":{"_account_id":35099,"name":"Jakub Jelinek","email":"jakub.jelinek@cern.ch","username":"kubajj"},"change_message_id":"6423b2cad50b10d872eec72ed60b4851133bb9a4","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The fix for the bug 2073406 - Incorrect name assigned to software raid device."},{"line_number":5,"context_line":"    The use of md_device as the default volume name if the volume name of a RAID"},{"line_number":6,"context_line":"    array hasn\u0027t been specified caused a \u0027Not POSIX compatible\u0027 error."},{"line_number":7,"context_line":"    This has been fixed by using just the last part of the md_device."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"4870a4f0_6a4b35d4","line":4,"in_reply_to":"94ef5890_94696aa3","updated":"2025-01-16 09:35:16.000000000","message":"Done","commit_id":"441be20683e41f6eb7f89a245731a815d4389397"}]}