public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Introducing a GDB Code Of Conduct
Date: Sat, 2 Dec 2023 20:15:13 -0700	[thread overview]
Message-ID: <20231202201513.2d2adef3@f39-zbm-nv> (raw)
In-Reply-To: <87edg7nsen.fsf@redhat.com>

On Thu, 30 Nov 2023 15:59:44 +0000
Andrew Burgess <aburgess@redhat.com> wrote:

> The text of the proposed CoC can be found at the end of this email, and
> I look forward to hearing people's thoughts.

I'm in favor of adopting this code of conduct.

Kevin


  reply	other threads:[~2023-12-03  3:15 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 [this message]
2023-12-03  3:26 ` Mike Frysinger
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=20231202201513.2d2adef3@f39-zbm-nv \
    --to=kevinb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).