)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"6707eed24c3f16662635feb4a91b7f098819b7ea","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e4e6e89e_7d9454d0","updated":"2023-02-26 21:23:19.000000000","message":"Tomas, could you please comment on this?\n\nAll the patches in this series are \u0027almost\u0027 trivial, but this one (and few other in the series) add a change.\nTCL uses either spaces and/or LF (\u0027\\n\u0027) as separators.\nInstead of using the jimtcl API to build a TCL dictionary or a TCL list, I create the text output with a special mix of spaces and LF\u0027s. This make the output readable by humans, while keeping it valid as TCL data.\nI don\u0027t see any drawback in the re-format of the output, apart from an IDE that could have to change the way to parse it.\nBut here we are talking about OpenOCD commands like \u0027flash list\u0027, \u0027rtt channellist\u0027, \u0027cti names\u0027, \u0027jtag names\u0027, \u0027dap names\u0027, \u0027tpiu names\u0027, \u0027target types\u0027 and \u0027target names\u0027. I don\u0027t expect them to be so relevant from IDE side.","commit_id":"eca69ee75f609f4442287b32e601c1d81d436087"},{"author":{"_account_id":1000687,"name":"Tomas Vanek","display_name":"Tomas Vanek","email":"vanekt@fbl.cz","username":"vanekt"},"change_message_id":"143d4a0155b17c199eecda6a5bcc25bb7874f17b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"aaa46a63_15bd10df","in_reply_to":"e4e6e89e_7d9454d0","updated":"2023-03-13 11:43:42.000000000","message":"Not sure about IDEs and what they parse. Let\u0027s merge the change a will see if any complaint hits the bug tracker.","commit_id":"eca69ee75f609f4442287b32e601c1d81d436087"}]}