bugs  

Messages by Thread

• Documentation | POSIX Compliance Navigation Tree is Wrong (#86) Joel Sherrill (@joel)
  • Re: Documentation | POSIX Compliance Navigation Tree is Wrong (#86) Amar Takhar (@amar)
• Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Chris Johns (@chris)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Chris Johns (@chris)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Draft: Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Gedare Bloom (@gedare)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Sebastian Huber (@sebhub)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
  • Re: Documentation | Convert files from reST to MarkDown (!155) Amar Takhar (@amar)
• Re: RTEMS Source Builder | Update GDB on RTEMS 5 (#14) Chris Johns (@chris)
  • Re: RTEMS Source Builder | Update GDB on RTEMS 5 (#14) Chris Johns (@chris)
• RTEMS | RTEMS Release 6.1 build error texinfo-7.0.3 on arm64-apple-darwin24.3.0-1 (#5218) Heinz Junkes (@junkes)
  • Re: RTEMS | RTEMS Release 6.1 build error texinfo-7.0.3 on arm64-apple-darwin24.3.0-1 (#5218) Heinz Junkes (@junkes)
  • Re: RTEMS | RTEMS Release 6.1 build error texinfo-7.0.3 on arm64-apple-darwin24.3.0-1 (#5218) Heinz Junkes (@junkes)
  • Re: RTEMS | RTEMS Release 6.1 build error texinfo-7.0.3 on arm64-apple-darwin24.3.0-1 (#5218) Chris Johns (@chris)
• RTEMS | gitlab: Add missed files to ignore (!427) Amar Takhar (@amar)
  • Re: RTEMS | gitlab: Add missed files to ignore (!427) Amar Takhar (@amar)
  • Re: RTEMS | gitlab: Add missed files to ignore (!427) Gedare Bloom (@gedare)
  • Re: RTEMS | gitlab: Add missed files to ignore (!427) Gedare Bloom (@gedare)
• Documentation | build: Add support for specifying which documents (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying which documents (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying which documents (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying which documents (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying which documents (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Kinsey Moore (@opticron)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Kinsey Moore (@opticron)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Amar Takhar (@amar)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Kinsey Moore (@opticron)
  • Re: Documentation | build: Add support for specifying documents to build (!154) Kinsey Moore (@opticron)
• Re: RTEMS Source Builder | Tooling Support Needed to Ease Updates to RSB Bset files (#80) Shreyansh Singh (@Shreyansh11)
  • Re: RTEMS Source Builder | Tooling Support Needed to Ease Updates to RSB Bset files (#80) Gedare Bloom (@gedare)
• RTEMS | m68k/uC5252: (#5217) Joel Sherrill (@joel)
  • Re: RTEMS | m68k/uC5252: __atomic_test_and_set undefined (#5217) Joel Sherrill (@joel)
  • Re: RTEMS | m68k/uC5252: __atomic_test_and_set undefined (#5217) Joel Sherrill (@joel)
• RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Sebastian Huber (@sebhub)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Sebastian Huber (@sebhub)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Sebastian Huber (@sebhub)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Amar Takhar (@amar)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Amar Takhar (@amar)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Amar Takhar (@amar)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Amar Takhar (@amar)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Joel Sherrill (@joel)
  • Re: RTEMS | libfdt: Replace deprecated 0-length arrays with proper flexible arrays (!426) Joel Sherrill (@joel)
• Re: LibBSD | Port libipsec and setkey to main (!40) Ning Yang (@yangn0)
  • Re: LibBSD | Port libipsec and setkey to main (!40) Kinsey Moore (@opticron)
• Re: RTEMS | Should all PPC BSPs build with -mstrict-align? (#3767) Giles Knap (@gilesknap)
  • Re: RTEMS | Should all PPC BSPs build with -mstrict-align? (#3767) Giles Knap (@gilesknap)
• RTEMS | build: Provide LDFLAGS for pkg-config (!425) Sebastian Huber (@sebhub)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!425) Sebastian Huber (@sebhub)
• RTEMS | cpukit/jffs2/rtime: Fix off-by-one error in decompression check (!424) Sebastian Huber (@sebhub)
  • Re: RTEMS | cpukit/jffs2/rtime: Fix off-by-one error in decompression check (!424) Sebastian Huber (@sebhub)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!424) Sebastian Huber (@sebhub)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!424) Amar Takhar (@amar)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!424) Amar Takhar (@amar)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!424) Amar Takhar (@amar)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!424) Amar Takhar (@amar)
  • Re: RTEMS | build: Provide LDFLAGS for pkg-config (!424) Amar Takhar (@amar)
• RTEMS | cpukit/jffs2/rtime: Fix off-by-one error in decompression check (!423) Sebastian Huber (@sebhub)
  • Re: RTEMS | cpukit/jffs2/rtime: Fix off-by-one error in decompression check (!423) Sebastian Huber (@sebhub)
  • Re: RTEMS | cpukit/jffs2/rtime: Fix off-by-one error in decompression check (!423) Sebastian Huber (@sebhub)
  • Re: RTEMS | cpukit/jffs2/rtime: Fix off-by-one error in decompression check (!423) Sebastian Huber (@sebhub)
• RTEMS Source Builder | Draft: rtems/config: Rename versioned tools to stable (!130) Kinsey Moore (@opticron)
  • Re: RTEMS Source Builder | Draft: rtems/config: Rename versioned tools to stable (!130) Kinsey Moore (@opticron)
  • Re: RTEMS Source Builder | Draft: rtems/config: Rename versioned tools to stable (!130) Chris Johns (@chris)
  • Re: RTEMS Source Builder | Draft: rtems/config: Rename versioned tools to stable (!130) Kinsey Moore (@opticron)
  • Re: RTEMS Source Builder | Draft: rtems/config: Rename versioned tools to stable (!130) Gedare Bloom (@gedare)
  • Re: RTEMS Source Builder | Draft: rtems/config: Rename versioned tools to stable (!130) Kinsey Moore (@opticron)
• Google Summer of Code | Add packaging options to RTEMS Deployment (#82) Chris Johns (@chris)
• RTEMS Source Builder | Follow-up from "rtems/config: Rename 8 to edge" regarding alteration of the stable tools directory structure (#94) Kinsey Moore (@opticron)
• Main Website | development: Add GSoC 2025 message and link (!5) Chris Johns (@chris)
  • Re: Main Website | development: Add GSoC 2025 message and link (!5) Chris Johns (@chris)
  • Re: Main Website | development: Add GSoC 2025 message and link (!5) Amar Takhar (@amar)
  • Re: Main Website | development: Add GSoC 2025 message and link (!5) Chris Johns (@chris)
  • Re: Main Website | development: Add GSoC 2025 message and link (!5) Chris Johns (@chris)
  • Re: Main Website | development: Add GSoC 2025 message and link (!5) Amar Takhar (@amar)
• Documentation | user/bsps: add note about beatnik (!153) Gedare Bloom (@gedare)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Gedare Bloom (@gedare)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Kinsey Moore (@opticron)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Kinsey Moore (@opticron)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Amar Takhar (@amar)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Amar Takhar (@amar)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Amar Takhar (@amar)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Amar Takhar (@amar)
  • Re: Documentation | user/bsps: add note about beatnik (!153) Kinsey Moore (@opticron)
• Release | notes/rtems-notes-6.2: Start notes for 6.2 release (!25) Gedare Bloom (@gedare)
  • Re: Release | notes/rtems-notes-6.2: Start notes for 6.2 release (!25) Gedare Bloom (@gedare)
  • Re: Release | notes/rtems-notes-6.2: Start notes for 6.2 release (!25) Gedare Bloom (@gedare)
  • Re: Release | notes/rtems-notes-6.2: Start notes for 6.2 release (!25) Gedare Bloom (@gedare)
  • Re: Release | notes/rtems-notes-6.2: Start notes for 6.2 release (!25) Gedare Bloom (@gedare)
  • Re: Release | notes/rtems-notes-6.2: Start notes for 6.2 release (!25) Chris Johns (@chris)
• RTEMS | Obsolete mvme5500 in favor of Beatnik (#5216) Gedare Bloom (@gedare)
  • Re: RTEMS | Deprecate powerpc/mvme5500 in favor of powerpc/beatnik (#5216) Gedare Bloom (@gedare)
  • Re: RTEMS | Deprecate powerpc/mvme5500 in favor of powerpc/beatnik (#5216) Gedare Bloom (@gedare)
  • Re: RTEMS | Deprecate powerpc/mvme5500 in favor of powerpc/beatnik (#5216) Gedare Bloom (@gedare)
• RTEMS | Remove set_vector() across all architectures and BSPs (#5215) Joel Sherrill (@joel)
  • Re: RTEMS | Remove set_vector() across all architectures and BSPs (#5215) Yaseen Agha (@solvablehat)
  • Re: RTEMS | Remove set_vector() across all architectures and BSPs (#5215) Gedare Bloom (@gedare)
• RTEMS | powerpc/ss555: Correct prototype of Clock_isr (!422) Joel Sherrill (@joel)
  • Re: RTEMS | powerpc/ss555: Correct prototype of Clock_isr (!422) Joel Sherrill (@joel)
  • Re: RTEMS | powerpc/ss555: Correct prototype of Clock_isr (!422) Gedare Bloom (@gedare)
  • Re: RTEMS | powerpc/ss555: Correct prototype of Clock_isr (!422) Gedare Bloom (@gedare)
  • Re: RTEMS | powerpc/ss555: Correct prototype of Clock_isr (!422) Gedare Bloom (@gedare)
• Re: RTEMS | Obsolete mvme5500 in favor of Beatnik (#4160) Giles Knap (@gilesknap)
  • Re: RTEMS | Obsolete mvme5500 in favor of Beatnik (#4160) Andrew Johnson (@anj_anl.gov)
  • Re: RTEMS | Obsolete mvme5500 in favor of Beatnik (#4160) Gedare Bloom (@gedare)
• RTEMS Tools | gitlab: Add link to CI (!52) Amar Takhar (@amar)
  • Re: RTEMS Tools | gitlab: Add link to CI (!52) Amar Takhar (@amar)
  • Re: RTEMS Tools | gitlab: Add link to CI (!52) Chris Johns (@chris)
• RTEMS Tools | gitlab: Add link to CI (!51) Amar Takhar (@amar)
  • Re: RTEMS Tools | gitlab: Add link to CI (!51) Amar Takhar (@amar)
  • Re: RTEMS Tools | gitlab: Add link to CI (!51) Kinsey Moore (@opticron)
• RTEMS Source Builder | gitlab: Add link to CI (!129) Amar Takhar (@amar)
  • Re: RTEMS Source Builder | gitlab: Add link to CI (!129) Amar Takhar (@amar)
  • Re: RTEMS Source Builder | gitlab: Add link to CI (!129) Kinsey Moore (@opticron)
• RTEMS Source Builder | gitlab: Add link to CI (!128) Amar Takhar (@amar)
  • Re: RTEMS Source Builder | gitlab: Add link to CI (!128) Amar Takhar (@amar)
  • Re: RTEMS Source Builder | gitlab: Add link to CI (!128) Joel Sherrill (@joel)
  • Re: RTEMS Source Builder | gitlab: Add link to CI (!128) Joel Sherrill (@joel)
• Network Services | gitlab: Add link to CI (!17) Amar Takhar (@amar)
  • Re: Network Services | gitlab: Add link to CI (!17) Amar Takhar (@amar)
  • Re: Network Services | gitlab: Add link to CI (!17) Kinsey Moore (@opticron)
  • Re: Network Services | gitlab: Add link to CI (!17) Kinsey Moore (@opticron)
• Legacy Networking | gitlab: Add link to CI (!20) Amar Takhar (@amar)
  • Re: Legacy Networking | gitlab: Add link to CI (!20) Amar Takhar (@amar)
  • Re: Legacy Networking | gitlab: Add link to CI (!20) Kinsey Moore (@opticron)
• lwIP | gitlab: Add link to CI (!19) Amar Takhar (@amar)
  • Re: lwIP | gitlab: Add link to CI (!19) Kinsey Moore (@opticron)
  • Re: lwIP | gitlab: Add link to CI (!19) Kinsey Moore (@opticron)
• LittlevGL | gitlab: Add link to CI (!9) Amar Takhar (@amar)
  • Re: LittlevGL | gitlab: Add link to CI (!9) Amar Takhar (@amar)
  • Re: LittlevGL | gitlab: Add link to CI (!9) Christian Mauderer (@c-mauderer)
• LibBSD | gitlab: Add link to CI (!64) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!64) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!64) Kinsey Moore (@opticron)
• LibBSD | gitlab: Add link to CI (!63) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!63) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!63) Kinsey Moore (@opticron)
• LibBSD | gitlab: Add link to CI (!62) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!62) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!62) Kinsey Moore (@opticron)
• LibBSD | gitlab: Add link to CI (!61) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!61) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!61) Kinsey Moore (@opticron)
• LibBSD | gitlab: Add link to CI (!60) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!60) Amar Takhar (@amar)
  • Re: LibBSD | gitlab: Add link to CI (!60) Kinsey Moore (@opticron)
  • Re: LibBSD | gitlab: Add link to CI (!60) Kinsey Moore (@opticron)
• Examples | gitlab: Add link to CI (!17) Amar Takhar (@amar)
  • Re: Examples | gitlab: Add link to CI (!17) Amar Takhar (@amar)
  • Re: Examples | gitlab: Add link to CI (!17) Kinsey Moore (@opticron)
  • Re: Examples | gitlab: Add link to CI (!17) Kinsey Moore (@opticron)
• Examples | gitlab: Add link to CI (!16) Amar Takhar (@amar)

• Earlier messages
• Later messages