Re: [rtems-docs PATCH] sphinx/style: Fix building with the latest sphinx

2023-12-19 Thread Chris Johns
On 20/12/2023 8:12 am, Joel Sherrill wrote: > I tried the patch on Rocky 9 with Python 3.9.14 and sphinx-build  5.3.0 from a > pip local install. > > (rtemsdocs) [joel@localhost rtems-docs]$ ./waf distclean > Waf: The wscript in '/home/joel/rtems-work/rtems-docs' is unreadable > Traceback (most

Re: [rtems-docs commit] sphinx/style: Fix building with the latest sphinx

2023-12-19 Thread Joel Sherrill
It didn't work on the CentOS 7 system because Chris pushed while I was switching VMs. I now get the same output on CentOS 7 as on Rocky 9. It has sphinx-build 5.3.0 --joel On Tue, Dec 19, 2023 at 3:10 PM Chris Johns wrote: > Module:rtems-docs > Branch:master > Commit:

Re: [rtems-docs PATCH] sphinx/style: Fix building with the latest sphinx

2023-12-19 Thread Joel Sherrill
I tried the patch on Rocky 9 with Python 3.9.14 and sphinx-build 5.3.0 from a pip local install. (rtemsdocs) [joel@localhost rtems-docs]$ ./waf distclean Waf: The wscript in '/home/joel/rtems-work/rtems-docs' is unreadable Traceback (most recent call last): File

Re: style patches - discuss

2023-12-19 Thread Gedare Bloom
On Thu, Dec 7, 2023 at 12:19 AM Sebastian Huber wrote: > > Hello, > > it seems we still have no tool and configuration to get satisfying > results when applied to existing RTEMS source files. May I suggest a > more pragmatic approach which focuses on new files. Would it be an > option to simply

Re: [rtems-docs PATCH] user: Automatic version number fixes

2023-12-19 Thread Gedare Bloom
lgtm, thanks On Mon, Dec 18, 2023 at 7:59 PM wrote: > > From: Chris Johns > > Updates #4695 > --- > user/exe/initialization.rst| 3 +-- > user/tracing/captureengine.rst | 20 ++-- > user/tracing/examples.rst | 12 ++-- > 3 files changed, 17 insertions(+), 18

Re: [PATCH] glossary: Add terms

2023-12-19 Thread Sebastian Huber
On 29.11.23 09:13, Sebastian Huber wrote: On 28.11.23 20:49, andrew.butterfi...@scss.tcd.ie wrote:     +    scenario     +        In a setting that involves many concurrent tasks that     interleave in arbitrary     +        ways, a scenario describes a single specific possible