gdb branch policy in non-gdb code
Mike Frysinger via Gdb <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <Yd3Xso52k7I2KbZI@vapier> |
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
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmHd17IACgkQQWM7n+g3 9YH4nQ/9EcHA0iJUhxE+3R0SGB+yOY4qZVAV1j4/A9ALTAdEfvSvl92KCNlR4/bH d+Mw653dU/AAhWJq/AWTCg6ynBBwZOiSS3Q/rEWYL9KY165EF+aQWtuLDemUv2PL vv7T9XBAO8HsVjnIVpqalc7hJfG4bQ6e2T4XeCjfF2wigfuehClitQQE1f7QmexM /UJ0IxfXlRGFThmh6rQonQN2tqTUe7b0StRju5DPSiBwBZknj5eqw5iYfUA90ZKc 8nBiZ6ONpSipN5NMILWG88TCQxJ21maUVEYqHHF3ozuMBccH8jjjrH3UNo3JFWza QgDdONwNNWmRwOXpCOQ3bPjwBcEOcBrFSdb5+g+Hy44fvZ6oE3F9cTG1/E20iv5K RruV/xqergClC/9bTbp9NPRUu+zAA0vGCKPra9BbRlMykBX8j2ShOytgaEW/HnxD AIXUzlwsuok2RKEIuYZRWuYY77kq1UFwlYWedKFiecBspduf1JCDCsplbpPWtMaz SlfOtp4fCvlWx8AwlxMnIcJ0K2o7uGJMAAxR5Ab2Cp0pIYjvn/Wy5fyeF3clvGIS qLhSN6onW3fBn6Rvi26gkVQ7SPjlJBOzC0l/DSX2gtKCpJW0O2RAmzwuZPrIZysA LUmAZm0iriUceUnMLb57ACr2mt4/odmMp3WW2X/REbjPBPvMrXY= =VgT0 -----END PGP SIGNATURE-----