From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Introducing a GDB Code Of Conduct
Date: Sat, 2 Dec 2023 22:26:48 -0500 [thread overview]
Message-ID: <ZWv1eOG5UAfYYnEp@vapier> (raw)
In-Reply-To: <87edg7nsen.fsf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-03 3:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 15:59 Andrew Burgess
2023-12-03 3:15 ` Kevin Buettner
2023-12-03 3:26 ` Mike Frysinger [this message]
2023-12-03 6:40 ` Eli Zaretskii
2023-12-04 15:49 ` Andrew Burgess
2023-12-04 9:27 ` Guinevere Larsen
2023-12-04 17:50 ` John Baldwin
2023-12-22 11:24 ` Andrew Burgess
2023-12-22 16:57 ` Guinevere Larsen
2023-12-22 19:39 ` Mike Frysinger
2024-04-05 20:32 ` Guinevere Larsen
2024-04-08 10:35 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZWv1eOG5UAfYYnEp@vapier \
--to=vapier@gentoo.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox