OK I would prefer to have it close a ticket on 5.1 that addresses the fact it was a latent bug. I'm not sure how to feel about having commits made prior to cutting a release, that update tickets for milestones after the release. I suppose it is just a minor annoyance to me.
On Fri, Apr 17, 2020 at 12:35 AM Christian Mauderer <christian.maude...@embedded-brains.de> wrote: > > Hello Gedare, > > On 16/04/2020 21:16, Gedare Bloom wrote: > > You can push this to 5.1, update the ticket milestone if you do. > > Thanks. In that case I most likely should create an extra ticket. I'm > not sure whether Sebastian sees that one as close enough to finished to > be a 5.1 ticket. For me it was a fix for the feature in progress and > therefore I updated that ticket. > > Best regards > > Christian > > > > > On Thu, Apr 16, 2020 at 9:27 AM Sebastian Huber > > <sebastian.hu...@embedded-brains.de> wrote: > >> > >> On 16/04/2020 15:29, Christian Mauderer wrote: > >>> _CPU_Counter_frequency() can be called by the rtems_counter > >>> initialization before arm_gt_clock_initialize() initializes the value > >>> used in _CPU_Counter_frequency(). > >>> > >>> Update #3456. > >> Thanks, looks good. > >> _______________________________________________ > >> devel mailing list > >> devel@rtems.org > >> http://lists.rtems.org/mailman/listinfo/devel > > -- > -------------------------------------------- > embedded brains GmbH > Herr Christian Mauderer > Dornierstr. 4 > D-82178 Puchheim > Germany > email: christian.maude...@embedded-brains.de > Phone: +49-89-18 94 741 - 18 > Fax: +49-89-18 94 741 - 08 > PGP: Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
