<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Joel,<div class=""><br class=""></div><div class="">I followed all of Chris’ instructions as much as I understood:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" style="font-family: SabonRoman;" class="">On 2017-November-16, at 21:21, Chris Johns <<a href="mailto:chrisj@rtems.org" class="">chrisj@rtems.org</a>> wrote:<br class=""><br class="">On 17/11/2017 15:05, <a href="mailto:groups@chichak.ca" class="">groups@chichak.ca</a> wrote:<br class=""><blockquote type="cite" class=""><br class="">(I don’t know how to proceed with getting this reported/fixed.)<br class=""><br class=""></blockquote><br class="">Please head to the wiki (<a href="https://devel.rtems.org/" class="">https://devel.rtems.org/</a>) and select the link in the<br class="">"Reporting a bug" column of the Releases Table for the release you are reporting<br class="">the bug against. You will need an account.<br class=""><br class="">- Clone the git repo and select the branch.<br class="">- Make the change and test.<br class="">- Commit the change with a summary as the first line and then if<br class="">you need more detail add a body. End the commit message with<br class="">"Close #12345." with the ticket number.<br class=""> eg git commit<br class=""> libmisc: Fix formatting in Stack_check_Dump_threads_usage<br class=""> Close #12345.<br class="">- Enter 'git format-patch -1'<br class="">- Attach the patch to the ticket.<br class=""><br class=""></blockquote><div class=""><br class=""></div>I guess I didn’t understand. I thought I needed to attach the diff to the ticket and some god-like person would do the final vet and push into the repo. No?</div><div class=""><br class=""></div><div class="">A</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 2017-December-05, at 14:17, RTEMS trac <<a href="mailto:trac@rtems.org" class="">trac@rtems.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">#3240: cpukit/libmisc/stackchk/check.c stack addresses formatted incorrectly.<br class="">----------------------------------------------+---------------------<br class=""> Reporter: Andrei Chichak | Owner: (none)<br class=""> Type: defect | Status: new<br class=""> Priority: normal | Milestone: 5.1<br class="">Component: lib | Version: 5<br class=""> Severity: normal | Resolution:<br class=""> Keywords: rtems_stack_checker_report_usage |<br class="">----------------------------------------------+---------------------<br class=""><br class="">Comment (by Joel Sherrill):<br class=""><br class=""> Wasn't a fix for this committed? Is there work left to do? Either close or<br class=""> state actions left. Please<br class=""><br class="">--<br class="">Ticket URL: <<a href="http://devel.rtems.org/ticket/3240#comment:2" class="">http://devel.rtems.org/ticket/3240#comment:2</a>><br class="">RTEMS Project <<a href="http://www.rtems.org/" class="">http://www.rtems.org/</a>><br class="">RTEMS Project<br class=""></div></div></blockquote></div><br class=""></div></body></html>