public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Richard Earnshaw (lists) via Binutils" <binutils@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
	 Nick Clifton <nickc@redhat.com>,
	"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
	ganandan@redhat.com,  markobri@redhat.com
Subject: Re: Binutils Code of Conduct
Date: Tue, 03 Oct 2023 11:52:44 -0600	[thread overview]
Message-ID: <87fs2rzj83.fsf@tromey.com> (raw)
In-Reply-To: <4f7fd5dc-ea33-95f0-a2e1-44cef841a418@arm.com> (Richard Earnshaw via Binutils's message of "Tue, 3 Oct 2023 10:54:39 +0100")

>>>>> "Richard" == Richard Earnshaw (lists) via Binutils <binutils@sourceware.org> writes:

Richard> I realize that we have separate projects, each with slightly different
Richard> governance structures, but I'd really like to see *one* CoC that
Richard> covers all of the GNU toolchain components - gcc, glibc, binutils and
Richard> gdb - rather than one for each which is nearly, but not quite the
Richard> same.  Yes, each component can have a different committee, as needed
Richard> (and that might lead to slightly different interpretations), but
Richard> having identical policies would help foster better understanding and
Richard> compliance IMO.

I'd support this as well.

thanks,
Tom

  parent reply	other threads:[~2023-10-03 17:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 16:02 Nick Clifton
2023-09-28 19:27 ` Alexandre Oliva
2023-09-28 20:42   ` Carlos O'Donell
2023-09-28 23:12     ` Alexandre Oliva
2023-09-28 23:35   ` Mark Wielaard
2023-09-29 13:39   ` Nick Clifton
2023-09-29 15:03     ` Matt Rice
2023-09-29 17:30     ` Alexandre Oliva
2023-09-28 20:27 ` Carlos O'Donell
2023-10-03  9:54   ` Richard Earnshaw (lists)
2023-10-03 10:36     ` Nick Clifton
2023-10-03 17:52     ` Tom Tromey [this message]
2023-09-29 12:52 ` Gomathi Anandan

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=87fs2rzj83.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=binutils@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=ganandan@redhat.com \
    --cc=markobri@redhat.com \
    --cc=nickc@redhat.com \
    /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).