This is an automated email from Gerrit. "Marc Schink <[email protected]>" just uploaded a new patch set to Gerrit, which you can find at https://review.openocd.org/c/openocd/+/9388
-- gerrit commit a9437241bef564b1dc68aa546b63b3c9074437a4 Author: Marc Schink <[email protected]> Date: Mon Sep 1 11:04:36 2025 +0200 README: Use Markdown extension Ensures proper rendering on GitHub [1] / GitLab, clarifies that Markdown syntax is expected from contributors, and enables editor syntax highlighting. [1] https://github.com/openocd-org/openocd Change-Id: Icaff52ed2bf7d6f32b5812b5aff1c081e8b7507a Signed-off-by: Marc Schink <[email protected]> diff --git a/Makefile.am b/Makefile.am index 845543721d..2e7bdc5cce 100644 --- a/Makefile.am +++ b/Makefile.am @@ -63,8 +63,8 @@ EXTRA_DIST += \ BUGS \ HACKING \ NEWTAPS \ - README.Windows \ - README.macOS \ + README.Windows.md \ + README.macOS.md \ $(EXTRA_DIST_NEWS) \ Doxyfile.in \ LICENSES/license-rules.txt \ diff --git a/README.Windows b/README.Windows.md similarity index 97% rename from README.Windows rename to README.Windows.md index 293eed975c..b0d4e085f7 100644 --- a/README.Windows +++ b/README.Windows.md @@ -5,7 +5,7 @@ You can build OpenOCD for Windows natively with either MinGW-w64/MSYS or Cygwin (plain MinGW might work with --disable-werror but is not recommended as it doesn't provide enough C99 compatibility). Alternatively, one can cross-compile it using MinGW-w64 on a *nix -host. See README for the generic instructions. +host. See README.md for the generic instructions. Also, the MSYS2 project provides both ready-made binaries and an easy way to self-compile from their software repository out of the box. diff --git a/README.macOS b/README.macOS.md similarity index 97% rename from README.macOS rename to README.macOS.md index 91d5e9261b..cc1e1c7332 100644 --- a/README.macOS +++ b/README.macOS.md @@ -41,7 +41,7 @@ MacPorts' libraries, so run configure like this: LDFLAGS=-L/opt/local/lib CPPFLAGS=-I/opt/local/include ./configure [options] -See README for the generic building instructions. +See README.md for the generic building instructions. If you're using a USB adapter and have a driver kext matched to it, you will need to unload it prior to running OpenOCD. E.g. with Apple diff --git a/README b/README.md similarity index 100% rename from README rename to README.md diff --git a/doc/openocd.texi b/doc/openocd.texi index 2199760e24..d90c8af592 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -239,7 +239,7 @@ needing a Git client: @uref{http://repo.or.cz/w/openocd.git} -The @file{README} file contains the instructions for building the project +The @file{README.md} file contains the instructions for building the project from the repository or a snapshot. Developers that want to contribute patches to the OpenOCD system are diff --git a/tools/scripts/checkpatch.pl b/tools/scripts/checkpatch.pl index 89f0a21783..9232c83a37 100755 --- a/tools/scripts/checkpatch.pl +++ b/tools/scripts/checkpatch.pl @@ -1417,14 +1417,14 @@ sub top_of_kernel_tree { if (!$OpenOCD) { my @tree_check = ( "COPYING", "CREDITS", "Kbuild", "MAINTAINERS", "Makefile", - "README", "Documentation", "arch", "include", "drivers", + "README.md", "Documentation", "arch", "include", "drivers", "fs", "init", "ipc", "kernel", "lib", "scripts", ); } # !$OpenOCD # OpenOCD specific: Begin my @tree_check = ( "AUTHORS", "BUGS", "COPYING", "HACKING", "Makefile.am", - "README", "contrib", "doc", "src", "tcl", "testing", "tools", + "README.md", "contrib", "doc", "src", "tcl", "testing", "tools", ); # OpenOCD specific: End --
