)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"b8fc9719924397661e18c00a62d41cddd5257a1c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"5e578aac_2e7f08a2","updated":"2026-01-25 13:34:48.000000000","message":"Is there any reason for using UTF-8 chars in the `README.md` file?\nIt was plain ASCII before this change","commit_id":"5bf2241f876e6f2e13dfe25ce23669151a65979e"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"38824ad508ffa769c92a4aac964ac8b4117173ed","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"41f59842_700c232a","in_reply_to":"5e578aac_2e7f08a2","updated":"2026-01-25 20:24:51.000000000","message":"Not really, no. They\u0027re probably just leftovers from when I was testing various (Markdown) editors.","commit_id":"5bf2241f876e6f2e13dfe25ce23669151a65979e"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"032beb8322b3cf5f588136f29390588068366b24","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"8c11c163_387d4277","updated":"2026-01-26 07:35:11.000000000","message":"Just a small correction to satisfy the linter.","commit_id":"31c8c0f58e43346d50ae9af3894b0d1c3c372b76"}],"README.md":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"f7db4944bf4b270e66a9e0b797f84ab250c92071","unresolved":true,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"9dcee935_c471455c","line":82,"updated":"2026-01-21 13:20:46.000000000","message":"I would prefer not having such extremely long lines. Markdown is able to reformat this even if it is split across lines\nSame for next line below","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"6e5ae45c2d66ce841f6733a8c815ba6ac932623f","unresolved":false,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"3cd3ed66_6ab3fd22","line":82,"in_reply_to":"059627cc_e69a1446","updated":"2026-01-25 10:51:53.000000000","message":"\u003e What about markdown static checkers? Does them exist? Should we use one here?\n\nhttps://pypi.org/project/pymarkdownlnt/ works fine and seems active and well maintained.\nI will push lint-error free version of our *.md files as addtional patches later.\n\nNot sure if local integration makes sense, this adds Python as requirement (in addition to Perl) for contributers.\nMaybe we could check only on Jenkins?\n\n\u003e We already have such issue in doc/openocd.texi. It\u0027s kind of annoying, but gerrit diff uses color highlights that helps reviewing multi-line text changes.\n\u003e I\u0027m not really in favor of such long lines. Depending on editor setup, the display of the long line can go off-screen, or editor could automatically split the long line to stay in the predefined width...\n\u003e ...\n\u003e Should this file go back to 72-80 char/line?\n\nAgreed, and since pymarkdownlnt complains about long lines I would stick with 80 chars/line.\nWhat about line breaks after a sentence? Maybe this enhances readability and review a bit?","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"38824ad508ffa769c92a4aac964ac8b4117173ed","unresolved":false,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"c58ba16c_cc300808","line":82,"in_reply_to":"06adc98c_ef4c6cc5","updated":"2026-01-25 20:24:51.000000000","message":"\u003e We already require python for the SPDX checker tools/scripts/spdxcheck.py taken from Linux kernel. But it is run only if there is a valid Python3 installed on host.\n\nYep, that\u0027s true.\n\n\u003e I don\u0027t see pymarkdownlnt as a problem, but we should still check for Python installed.\n\nAgree, but `pymarkdownlnt` comes as \"executable\" installed via pip. So we can simply check for that I think.\n\n\u003e What about line breaks after a sentence?\n\u003e Which syntax? https://www.markdownguide.org/basic-syntax/\n\u003e [...]\n\nMy mistake... the question referred to long lines compared to 80 chars/line.\nAs a compromise between long lines without breaks and 80 characters, I would suggest starting each sentence on a new line (see my latest patch set).\nThis makes git diff a little clearer when we change sentences.\nThis is intended as a general guideline and is not specific to Markdown.\nAny objections to this?","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"b8fc9719924397661e18c00a62d41cddd5257a1c","unresolved":false,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"06adc98c_ef4c6cc5","line":82,"in_reply_to":"3cd3ed66_6ab3fd22","updated":"2026-01-25 13:34:48.000000000","message":"\u003e Not sure if local integration makes sense, this adds Python as requirement (in addition to Perl) for contributers.\n\nWe already require python for the SPDX checker `tools/scripts/spdxcheck.py` taken from Linux kernel. But it is run only if there is a valid Python3 installed on host.\nI don\u0027t see `pymarkdownlnt` as a problem, but we should still check for Python installed.\n\n\u003e What about line breaks after a sentence?\n\nWhich syntax? https://www.markdownguide.org/basic-syntax/\nreports few possible ways:\n- double trailing white-space at end of line (ugly, incompatible with checkpatch, not always visible in an editor)\n- `\u003c/br\u003e` at end of line\n- `\\` backslash at end of line (ugly, looks like line continuation for C macros)\n- blank line (paragraph delimiter)\n\nMy preferences are for blank line and, when really needed for readability, `\u003c/br\u003e`","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"37d4efe8ecc2f71c88eeec96455079fd172155af","unresolved":false,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"059627cc_e69a1446","line":82,"in_reply_to":"521a3293_f32a9111","updated":"2026-01-25 09:58:19.000000000","message":"We already have such issue in `doc/openocd.texi`. It\u0027s kind of annoying, but gerrit diff uses color highlights that helps reviewing multi-line text changes.\nI\u0027m not really in favor of such long lines. Depending on editor setup, the display of the long line can go off-screen, or editor could automatically split the long line to stay in the predefined width...\n\nToday checkpatch checks the documentation for miss-spelled words, but not for line length. I consider it as a limitation of that script.\nShould this file go back to 72-80 char/line?\n\nOff topic: We don\u0027t need to improve checkpatch with static texi checker since we build the doc in jenkins.\nWhat about markdown static checkers? Does them exist? Should we use one here?","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"d5d2d95a283487e1c6b765ea1cdf55a172747a9b","unresolved":false,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"521a3293_f32a9111","line":82,"in_reply_to":"9dcee935_c471455c","updated":"2026-01-21 20:36:03.000000000","message":"You\u0027re absolutely right, I just published a WIP version without realizing it. The new version also corresponds to a documentation style that I would like to propose for the style guide. The basic idea is described very well here [1].\n\n[1] https://nick.groenen.me/notes/one-sentence-per-line/","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"561a6c7cfeccaa69c047b3833195272d3c5747e4","unresolved":false,"context_lines":[{"line_number":79,"context_line":"pacman -S mingw-w64-x86_64-openocd"},{"line_number":80,"context_line":"```"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where active development happens. “Packagers” create binary releases of OpenOCD after the developers publish new source code releases. Older OpenOCD versions are not suitable for diagnosing issues in the current release, so users should stay in touch with their distribution maintainers or interface vendors to ensure that appropriate updates are provided regularly."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"If you use one of these binary packages, you must contact the Packager for support or for newer binary versions; the OpenOCD developers do not provide direct support for packaged binaries."},{"line_number":85,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":3,"id":"97413d11_0fedd283","line":82,"in_reply_to":"c58ba16c_cc300808","updated":"2026-01-25 22:00:54.000000000","message":"I think it\u0027s ok!","commit_id":"82bf92c69c2e025c73ecb161458a3ed26139cbe3"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"b8fc9719924397661e18c00a62d41cddd5257a1c","unresolved":true,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"# Installing OpenOCD"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The easiest way to install OpenOCD is through your operating system’s package"},{"line_number":57,"context_line":"manager."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":" - **Debian / Ubuntu**"}],"source_content_type":"text/x-gfm","patch_set":5,"id":"3a01ca0a_6558630b","line":56,"updated":"2026-01-25 13:34:48.000000000","message":"the char between `system` and `s` is not ASCII","commit_id":"5bf2241f876e6f2e13dfe25ce23669151a65979e"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"561a6c7cfeccaa69c047b3833195272d3c5747e4","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"# Installing OpenOCD"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The easiest way to install OpenOCD is through your operating system’s package"},{"line_number":57,"context_line":"manager."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":" - **Debian / Ubuntu**"}],"source_content_type":"text/x-gfm","patch_set":5,"id":"7418b0ac_af0a36eb","line":56,"in_reply_to":"3a01ca0a_6558630b","updated":"2026-01-25 22:00:54.000000000","message":"Done","commit_id":"5bf2241f876e6f2e13dfe25ce23669151a65979e"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"b8fc9719924397661e18c00a62d41cddd5257a1c","unresolved":true,"context_lines":[{"line_number":82,"context_line":""},{"line_number":83,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where"},{"line_number":84,"context_line":"active development happens."},{"line_number":85,"context_line":"“Packagers” create binary releases of OpenOCD after the developers publish new"},{"line_number":86,"context_line":"source code releases."},{"line_number":87,"context_line":"Older OpenOCD versions are not suitable for diagnosing issues in the current"},{"line_number":88,"context_line":"release."}],"source_content_type":"text/x-gfm","patch_set":5,"id":"320fb8e5_e863d7ec","line":85,"updated":"2026-01-25 13:34:48.000000000","message":"The double quote around `Packagers` is not ASCII","commit_id":"5bf2241f876e6f2e13dfe25ce23669151a65979e"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"561a6c7cfeccaa69c047b3833195272d3c5747e4","unresolved":false,"context_lines":[{"line_number":82,"context_line":""},{"line_number":83,"context_line":"These packages are often more stable than the bleeding-edge Git mainline, where"},{"line_number":84,"context_line":"active development happens."},{"line_number":85,"context_line":"“Packagers” create binary releases of OpenOCD after the developers publish new"},{"line_number":86,"context_line":"source code releases."},{"line_number":87,"context_line":"Older OpenOCD versions are not suitable for diagnosing issues in the current"},{"line_number":88,"context_line":"release."}],"source_content_type":"text/x-gfm","patch_set":5,"id":"8b19da9d_8493602b","line":85,"in_reply_to":"320fb8e5_e863d7ec","updated":"2026-01-25 22:00:54.000000000","message":"Done","commit_id":"5bf2241f876e6f2e13dfe25ce23669151a65979e"}]}