gdb branch policy in non-gdb code

[Mike Frysinger]

the gdb docs are little unclear:
https://sourceware.org/gdb/wiki/Internals%20Releasing-GDB

it focuses on the gdb/ subdir.  that makes sense -- the gdb branch is meant
for releasing gdb, and most bugfixes will be in that directory.

but what about commits outside of gdb/ ?  does the gdb branch maintainer
have to approve each one ?  like something in bfd/ or libctf/ or sim/.
or is it good enough that it's already been approved & merged into master,
and the flow is more interested folks post a [committed] notification to
the list when they cherry-pick back ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/gdb/attachments/20220111/722fda8c/attachment.sig>