Where can I find the existing source code of generating release notes?

Chris, I am currently working on RTEMS release notes generator, can you give me some pointers to the existing source code of generating release notes? I am trying to generate the report from Trac like 4.11.3 release notes (​ https://ftp.rtems.org/pub/rtems/releases/4.11/4.11.3/rtems-4.11.3-releas

generating gcno files

Current status: The gcno files are needed to pass it as an argument to covoar to generate the gcov reports. the generation of the gcno file needs changing the gcc flags . reference link : https://gcc.gnu.org/onlinedocs/gcc/Gcov-Data-Files.html#Gcov-Data-Files -- vijay _

[PATCH] Rework to minimize and eventually eliminate RTEMS use of bsp_specs

--- gcc/config.gcc| 2 +- gcc/config/arm/rtems.h| 4 gcc/config/bfin/rtems.h | 4 gcc/config/i386/rtemself.h| 6 +- gcc/config/i386/rtemself64.h | 39 +++ gcc/config/m68k/rtemself.h| 4 gcc/config/mi

[PATCH 16/16] virtex5: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/virtex5/config/virtex5.cfg | 2 +- c/src/lib/libbsp/powerpc/virtex5/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/virtex5/config/virtex5.cfg b/bsps/powerpc/virtex5/config/virtex5.cfg index 6f039da..cb260db 100

[PATCH 12/16] t32mppc: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/t32mppc/config/t32mppc.cfg | 3 +-- c/src/lib/libbsp/powerpc/t32mppc/configure.ac | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/bsps/powerpc/t32mppc/config/t32mppc.cfg b/bsps/powerpc/t32mppc/config/t32mppc.cfg index 1bbfe76..a83dafd 1

[PATCH 14/16] virtex: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/virtex/config/virtex.cfg| 2 +- c/src/lib/libbsp/powerpc/virtex/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/virtex/config/virtex.cfg b/bsps/powerpc/virtex/config/virtex.cfg index 412b0da..c108b01 100644 --

[PATCH 07/16] mvme5500: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/mvme5500/config/mvme5500.cfg | 2 +- c/src/lib/libbsp/powerpc/mvme5500/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/mvme5500/config/mvme5500.cfg b/bsps/powerpc/mvme5500/config/mvme5500.cfg index 6a0fcea..0bfb6

[PATCH 01/16] beatnik: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/beatnik/config/beatnik.cfg | 2 +- c/src/lib/libbsp/powerpc/beatnik/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/beatnik/config/beatnik.cfg b/bsps/powerpc/beatnik/config/beatnik.cfg index 1190cad..05bea38 100

[PATCH 13/16] tqm8xx: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/tqm8xx/config/tqm8xx.inc| 3 +-- c/src/lib/libbsp/powerpc/tqm8xx/configure.ac | 1 + 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bsps/powerpc/tqm8xx/config/tqm8xx.inc b/bsps/powerpc/tqm8xx/config/tqm8xx.inc index f9a31d0..0887110 100644 -

[PATCH 04/16] mpc55xxevb: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/mpc55xxevb/config/mpc55xx.inc | 2 +- c/src/lib/libbsp/powerpc/mpc55xxevb/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/mpc55xxevb/config/mpc55xx.inc b/bsps/powerpc/mpc55xxevb/config/mpc55xx.inc index 5b0b843.

[PATCH 00/16] Remove use of -Dxxx in BSP CFLAGS

Hi This should remove the last uses of -D from the BSPs. With this, more PowerPC BSPs successfully build examples-v2. There is an rld issue which prevents some from building. This should close #3425 if all are OK. Joel Sherrill (16): beatnik: Move -Dxxx to configure.ac haleakala: Move -Dxxx

[PATCH 05/16] mpc8260ads: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/mpc8260ads/config/mpc8260ads.cfg| 3 +-- c/src/lib/libbsp/powerpc/mpc8260ads/configure.ac | 1 + 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bsps/powerpc/mpc8260ads/config/mpc8260ads.cfg b/bsps/powerpc/mpc8260ads/config/mpc8260ads.cfg index 4

[PATCH 06/16] mvme3100: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/mvme3100/config/mvme3100.cfg | 2 +- c/src/lib/libbsp/powerpc/mvme3100/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/mvme3100/config/mvme3100.cfg b/bsps/powerpc/mvme3100/config/mvme3100.cfg index 6e7c695..50a29

[PATCH 11/16] ss555: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/ss555/config/ss555.cfg | 3 +-- c/src/lib/libbsp/powerpc/ss555/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/bsps/powerpc/ss555/config/ss555.cfg b/bsps/powerpc/ss555/config/ss555.cfg index 1745bb5..7054eaa 100644 --- a/

[PATCH 03/16] motorola_powerpc: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/motorola_powerpc/config/mcp750.cfg | 2 +- bsps/powerpc/motorola_powerpc/config/mtx603e.cfg | 2 +- bsps/powerpc/motorola_powerpc/config/mvme2100.cfg | 2 +- bsps/powerpc/motorola_powerpc/config/qemuprep-altivec.cfg | 4 ++-- bsps/powe

[PATCH 02/16] haleakala: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/haleakala/config/haleakala.cfg | 2 +- c/src/lib/libbsp/powerpc/haleakala/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/haleakala/config/haleakala.cfg b/bsps/powerpc/haleakala/config/haleakala.cfg index 90b9292.

[PATCH 08/16] psim: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/psim/config/psim.cfg | 2 +- c/src/lib/libbsp/powerpc/psim/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/psim/config/psim.cfg b/bsps/powerpc/psim/config/psim.cfg index cb39949..1cfd201 100644 --- a/bsps/pow

[PATCH 09/16] qemuppc: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/qemuppc/config/qemuppc.cfg | 2 +- c/src/lib/libbsp/powerpc/qemuppc/configure.ac | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/qemuppc/config/qemuppc.cfg b/bsps/powerpc/qemuppc/config/qemuppc.cfg index f424ec2..5e919c1 1006

[PATCH 10/16] qoriq: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/qoriq/config/qoriq.inc | 3 +-- bsps/powerpc/qoriq/config/qoriq_e6500_32.cfg | 3 +-- bsps/powerpc/qoriq/config/qoriq_e6500_64.cfg | 3 +-- c/src/lib/libbsp/powerpc/qoriq/configure.ac | 2 +- 4 files changed, 4 insertions(+), 7 deletions(-) diff --git a/b

[PATCH 15/16] virtex4: Move -Dxxx to configure.ac

Updates #3425. --- bsps/powerpc/virtex4/config/virtex4.cfg | 2 +- c/src/lib/libbsp/powerpc/virtex4/configure.ac | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/bsps/powerpc/virtex4/config/virtex4.cfg b/bsps/powerpc/virtex4/config/virtex4.cfg index a893abe..88e50a6 100

Re: BSPs with Same Name, Different Architecture

On Wed, May 16, 2018 at 9:41 AM, Joel Sherrill wrote: > > > On Wed, May 16, 2018 at 6:32 AM, Joel Sherrill wrote: >> >> >> >> On Wed, May 16, 2018, 4:05 AM Chris Johns wrote: >>> >>> On 15/5/18 3:39 am, Joel Sherrill wrote: >>> > On Mon, May 14, 2018, 10:16 AM Gedare Bloom >> >

Re: BSPs with Same Name, Different Architecture

On Wed, May 16, 2018 at 6:32 AM, Joel Sherrill wrote: > > > On Wed, May 16, 2018, 4:05 AM Chris Johns wrote: > >> On 15/5/18 3:39 am, Joel Sherrill wrote: >> > On Mon, May 14, 2018, 10:16 AM Gedare Bloom > > > wrote: >> > >> > This is an excellent rule. BSP names sho

Re: GSOC Weekly IRC Meetings

This is a reminder that our first weekly IRC meeting will be held in about an hour. I'm unlikely to send future reminders. Gedare On Fri, May 11, 2018 at 10:05 AM, Gedare Bloom wrote: > The coding period officially opens on Monday, and we'll plan to hold > the first weekly IRC meeting for GSoC

Re: BSPs with Same Name, Different Architecture

On Wed, May 16, 2018, 4:05 AM Chris Johns wrote: > On 15/5/18 3:39 am, Joel Sherrill wrote: > > On Mon, May 14, 2018, 10:16 AM Gedare Bloom > > wrote: > > > > This is an excellent rule. BSP names should be unique. > > > > I am not sure the current logic ensures that

Re: BSPs with Same Name, Different Architecture

On 15/5/18 3:39 am, Joel Sherrill wrote: > On Mon, May 14, 2018, 10:16 AM Gedare Bloom > wrote: > > This is an excellent rule. BSP names should be unique. > > I am not sure the current logic ensures that but it did break one of my name > reuses. I did not intend to