From: Andrew Burgess <aburgess@redhat.com>
To: Guinevere Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Introducing a GDB Code Of Conduct
Date: Mon, 08 Apr 2024 11:35:05 +0100 [thread overview]
Message-ID: <87v84s16sm.fsf@redhat.com> (raw)
In-Reply-To: <d4ae0e6e-5ec7-4d06-aa61-e368f461eb50@redhat.com>
Guinevere Larsen <blarsen@redhat.com> writes:
>> Andrew Burgess <aburgess@redhat.com> writes:
>>
>> If you are willing to help out with this, then let me know and I'll get
>> you added in the New Year.
>>
>> Thanks,
>> Andrew
>>
> Has there been any movement regarding the CoC committee? We've had the
> page up for quite a while and it would be nice to populate it.
I've started a new thread on gdb-patches asking for volunteers,
hopefully that might get more attention ... and responses.
Thanks,
Andrew
prev parent reply other threads:[~2024-04-08 10:35 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
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 [this message]
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=87v84s16sm.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=blarsen@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).