RTEMS | rtems/event: regenerate from central (!444)

[Chris Johns (@chris)]

Chris Johns commented on a discussion on cpukit/include/rtems/rtems/event.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/444#note_121305

 >  /**
 >   * @brief This event set constant represents the reserved system event that is
 >   *   internally used by aio_suspend to notify of suspension termination.
 > - *
 > - * @par Constraints
 > - * @parblock
 > - * The following constraints apply to this constant:
 > - *
 > - * * The constant is not included in the pre-qualified feature set of RTEMS.
 > - *   Applications which are restricted to only use interfaces of the
 > - *   pre-qualified feature set of RTEMS shall not use the constant.
 > - * @endparblock
 >   */

I am sorry but I have no idea how this all works and what I can offer? Have I missed the discussion about handling of generated content from central?

The MR referenced is still open? How is this suppose to work? We allow generated output from MRs in another repo to be merged without the original MR being merged? It seems backwards to me.

I would prefer there is an agreed process for how central is managed than a merge here or there being mistaken as an acceptable procedure.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/444#note_121305
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250319/96fdeeac/attachment-0001.htm>