On 30 Nov 2023 15:59, Andrew Burgess wrote:
> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
> recently, and I believe that GDB should do likewise.

adopting a CoC sounds fine, but really seems like we should be using the
same one across them.  there isn't anything in the content that screams
"this only makes sense for XXX project".  can't we do this akin to how
we merge changes from "upstream" gcc tree ?

yes, i know there are a few things inline like "here's the gdb e-mail",
but that should be fairly trivial to summarize at the beginning/end, or
ideally in a sep file altogether to make merging trivial.
-mike