From: cgd@broadcom.com
To: cagney@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: [PATCH] sim/MAINTAINERS clarifications.
Date: Thu, 07 Mar 2002 12:26:00 -0000 [thread overview]
Message-ID: <yov5u1rsf7kr.fsf@broadcom.com> (raw)
I created the following question after starting to ask the question:
So, the sim MAINTAINERS file lists maintainers for 'common'.
Are they assumed to have mastership of sim/igen as well?
(I'm just wondering who the right person I should pester about a
quick approval for
http://sources.redhat.com/ml/gdb-patches/2002-03/msg00055.html,
since the common part of that is trivial and seems obviously useful,
to me. 8-)
Assuming the answer to that is "yes," and that the rest of the changes
below are desirable, how about this patch to sim/MAINTAINERS?
(the result is less greppable, but more in the style of the GDB
MAINTAINERS file.)
thanks,
chris
========
2002-03-07 Chris Demetriou <cgd@broadcom.com>
* MAINTAINERS: Tweak spacing. Note write-after-approval
and obvious fix policies. Note that "igen" is maintained
by the maintainers of "common". Note that "testsuite" bits
for particular sims are owned by those sims' maintainers.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/sim/MAINTAINERS,v
retrieving revision 1.9
diff -u -r1.9 MAINTAINERS
--- MAINTAINERS 2002/03/06 20:15:53 1.9
+++ MAINTAINERS 2002/03/07 20:24:13
@@ -1,19 +1,29 @@
- SIM Maintainers
+ SIM Maintainers
The simulator is part of the GDB project, so see the file
gdb/MAINTAINERS for general information about maintaining these files.
+(In particular, the same obvious fix and write after approval rules
+apply here.)
If you are considering contributing a patch, please see the file
gdb/CONTRIBUTE. Patches to these files should be posted to:
gdb-patches@sources.redhat.com
+
- Maintainers for particular sims:
+ Maintainers for particular sims and subdirectories:
arm Nick Clifton <nickc@redhat.com>
+
ppc Andrew Cagney <ac131313@redhat.com>
-ppc Geoff Keating <geoffk@redhat.com>
+ Geoff Keating <geoffk@redhat.com>
+
m68hc11 Stephane Carrez <Stephane.Carrez@worldnet.fr>
+
mips Andrew Cagney <ac131313@redhat.com>
-mips Chris Demetriou <cgd@broadcom.com>
-common Ben Elliston <bje@redhat.com>
-common Frank Ch. Eigler <fche@redhat.com>
+ Chris Demetriou <cgd@broadcom.com>
+
+common, igen Ben Elliston <bje@redhat.com>
+ Frank Ch. Eigler <fche@redhat.com>
+
+Sim maintainers are also maintainers of the directories in 'testsuite'
+which correspond to their sims.
next reply other threads:[~2002-03-07 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 12:26 cgd [this message]
2002-03-07 14:02 ` Andrew Cagney
2002-03-07 15:57 ` cgd
2002-03-07 14:23 ` Andrew Cagney
2002-03-07 18:12 ` Andrew Cagney
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=yov5u1rsf7kr.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=cagney@redhat.com \
--cc=gdb-patches@sources.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