)]}'
{"README.macOS.md":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"7bce7d54cbf0012cc6797a1f88a8e345f55372ea","unresolved":true,"context_lines":[{"line_number":24,"context_line":""},{"line_number":25,"context_line":"With Homebrew you can either run:"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"    brew install [--HEAD] openocd (where optional --HEAD asks brew to"},{"line_number":28,"context_line":"                                 install the current Git version)"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"or"}],"source_content_type":"text/x-markdown","patch_set":1,"id":"4e055e34_7f49dab7","line":27,"updated":"2026-01-26 09:40:36.000000000","message":"Should the text within parenthesis be moved in a separate line, as you did below?","commit_id":"f10ada0776ee5f3f0867a7abbac538ffd8267df5"},{"author":{"_account_id":1000853,"name":"Marc Schink","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"54808d80d3a3916fddc724fdbcdff000c99bb2a5","unresolved":false,"context_lines":[{"line_number":24,"context_line":""},{"line_number":25,"context_line":"With Homebrew you can either run:"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"    brew install [--HEAD] openocd (where optional --HEAD asks brew to"},{"line_number":28,"context_line":"                                 install the current Git version)"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"or"}],"source_content_type":"text/x-markdown","patch_set":1,"id":"9c374f26_b0932e61","line":27,"in_reply_to":"4e055e34_7f49dab7","updated":"2026-01-26 15:44:12.000000000","message":"Actually, I wanted to change as little as possible and just fix the linter errors. Anyway, fixed it.","commit_id":"f10ada0776ee5f3f0867a7abbac538ffd8267df5"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"7bce7d54cbf0012cc6797a1f88a8e345f55372ea","unresolved":true,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"You should also specify LDFLAGS and CPPFLAGS to allow `configure` to use"},{"line_number":42,"context_line":"MacPorts\u0027 libraries, so run configure like this:"},{"line_number":43,"context_line":"`LDFLAGS\u003d-L/opt/local/lib CPPFLAGS\u003d-I/opt/local/include ./configure [options]`"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"See [README](README.md) for the generic building instructions."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-markdown","patch_set":1,"id":"d889b898_53b03f5b","line":43,"updated":"2026-01-26 09:40:36.000000000","message":"Not sure, but I see you add a level of 4 space indentation before commands, but not here.\nIs the indentation needed here too, at least for consistency?","commit_id":"f10ada0776ee5f3f0867a7abbac538ffd8267df5"},{"author":{"_account_id":1000853,"name":"Marc Schink","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"54808d80d3a3916fddc724fdbcdff000c99bb2a5","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"You should also specify LDFLAGS and CPPFLAGS to allow `configure` to use"},{"line_number":42,"context_line":"MacPorts\u0027 libraries, so run configure like this:"},{"line_number":43,"context_line":"`LDFLAGS\u003d-L/opt/local/lib CPPFLAGS\u003d-I/opt/local/include ./configure [options]`"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"See [README](README.md) for the generic building instructions."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-markdown","patch_set":1,"id":"d966f4c0_3c762325","line":43,"in_reply_to":"7305d754_c3cf8185","updated":"2026-01-26 15:44:12.000000000","message":"\u003e Not sure, but I see you add a level of 4 space indentation before commands, but not here.\n\u003e Is the indentation needed here too, at least for consistency?\n\nGood catch, I overlooked this one. Thanks.\n\nI would prefer the extended syntax as it provides code-specific syntax highlighting. The extended syntax is widely supported: GitLab, GitHub, Sphinx, VSCode, and many backend libraries. It\u0027s also part of the commonmark specification, https://commonmark.org/.\nSo I don\u0027t think we run into incompatibility issues.\n\n\u003e I don\u0027t find the additional extension to add \"sh\" or \"gdb\" at the beginning of the code block.\n\nSee https://www.markdownguide.org/extended-syntax/#syntax-highlighting\nThe `sh` key for shell commands is widely supported (at least GitLab and GitHub), `gdb` is actually only used to make the linter happy.","commit_id":"f10ada0776ee5f3f0867a7abbac538ffd8267df5"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"bad6e72033aa2079530adbd3f9697608d889efff","unresolved":true,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"You should also specify LDFLAGS and CPPFLAGS to allow `configure` to use"},{"line_number":42,"context_line":"MacPorts\u0027 libraries, so run configure like this:"},{"line_number":43,"context_line":"`LDFLAGS\u003d-L/opt/local/lib CPPFLAGS\u003d-I/opt/local/include ./configure [options]`"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"See [README](README.md) for the generic building instructions."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-markdown","patch_set":1,"id":"7305d754_c3cf8185","line":43,"in_reply_to":"d889b898_53b03f5b","updated":"2026-01-26 09:55:15.000000000","message":"In next patch in this series you use another syntax for commands, that consists of a sequence of (cannot copy here because interpreted as formatting by gerrit):\n- 3 ASCII character 0x60 (grave accent)\n- text \"sh\"\n- newline\n- command string\n- newline\n- 3 ASCII character 0x60 (grave accent)\n\nThe \u0027basic\u0027 markdown syntax uses the 4 space prefix for code\nThe \u0027extended\u0027 markdown syntax uses to surround block of code with 3 ASCII character 0x60\nI don\u0027t find the additional extension to add \"sh\" or \"gdb\" at the beginning of the code block.\n\nShould we stick to the \u0027basic\u0027 markdown? Is there any compatibility risk to adopt \u0027extended\u0027 markdown?","commit_id":"f10ada0776ee5f3f0867a7abbac538ffd8267df5"}]}