public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: gdb maintainer commit rights
Date: Fri, 8 Apr 2022 20:56:01 +0930	[thread overview]
Message-ID: <YlAbySBzi8WNmgCs@squeak.grove.modra.org> (raw)

Formalise what ought to be obvious.  The top level of the binutils-gdb
repository isn't owned by binutils.  Just how far we might want to
diverge from the gcc repository top level files is another discussion.

	* MAINTAINERS: Spelling fix.  GDB global maintainer rights.

diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS
index ee3cdd01593..082b85f8e55 100644
--- a/binutils/MAINTAINERS
+++ b/binutils/MAINTAINERS
@@ -6,7 +6,7 @@ the assembler (gas), the profiler (gprof), a whole suite of other
 programs (binutils) and the libraries that they use (bfd and
 opcodes).  This project shares a common set of header files with the
 GCC and GDB projects (include), so maintainership of those files is
-shared amoungst the projects.
+shared amongst the projects.
 
 The home page for binutils is:
 
@@ -45,6 +45,10 @@ repository without obtaining approval first:
   Richard Sandiford <rdsandiford@googlemail.com>
   Jan Beulich <jbeulich@suse.com>
 
+GDB global maintainers also have permission to commit and approve
+patches to the top level files and to those parts of bfd files
+primarily used by GDB.
+
       --------- Maintainers ---------
 
 Maintainers are individuals who are responsible for, and have

-- 
Alan Modra
Australia Development Lab, IBM

                 reply	other threads:[~2022-04-08 11:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=YlAbySBzi8WNmgCs@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --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).