We will ensure this policy. This is a good reminder that we had encountered some problems last time with non-code churn caused by GCI 2015.
On Wed, Nov 7, 2018 at 1:40 AM, Chris Johns <chr...@rtems.org> wrote: > On 07/11/2018 17:36, Sebastian Huber wrote: > > It would be nice if GCI2018 patches are sent to devel@rtems.org for > review > > before they are committed. > > I agree. I will post to the gci mentors list asking if this can be done. > > Chris > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
