On 13.02.2026 16:47, Maciej W. Rozycki wrote: > On Fri, 13 Feb 2026, Jan Beulich wrote: > >>> OK to apply? Obviously correct probably. >> >> Probably, but it wants to go to gcc first. binutils syncs from there, if >> recurring entries in the history of configure.ac are to be trusted. > > We're clear on that, no need to deduce anything from the history: > > Makefile.*; configure; configure.ac; src-release > Any global maintainer can approve changes to these > files, but they should be aware that they need to > be kept in sync with their counterparts in the GCC > repository. Also please notify the following of > any committed patches: > [email protected] > [email protected] > > so applying the change at once across the board is considered fine and no > particular order is implied (any past discrepancies must have come from > the failure to follow the rule). This is also why I formulated the commit > description such as to be compatible with both repos and submitted this to > all the relevant mailing lists.
Well, the quote from ./MAINTAINERS - as nice as it may sound - still doesn't help in practice: E.g. me approving the change for binutils-gdb doesn't help at all, because in order to get the gcc counterpart updated you need approval there. Yet once the gcc counterpart was updated, sync-ing out copy imo wouldn't require any approval anymore. So for formality's sake: Okay for binutils-gdb once approved for gcc. Jan
