From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Clifton <nickc@redhat.com>,
Andrew Cagney <ac131313@redhat.com>,
Geoff Keating <geoffk@redhat.com>,
Andrew Cagney <ac131313@redhat.com>,
Chris Demetriou <cgd@broadcom.com>, Ben Elliston <bje@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb@sources.redhat.com
Subject: [maint] sim and common
Date: Tue, 05 Mar 2002 21:08:00 -0000 [thread overview]
Message-ID: <3C85A44B.6090403@cygnus.com> (raw)
Hello,
The sim/MAINTAINERS file contains:
> SIM Maintainers
>
> The simulator is part of the GDB project, so see the file
> gdb/MAINTAINERS for general information about maintaining these files.
>
> 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:
>
> arm Nick Clifton <nickc@redhat.com>
> ppc Andrew Cagney <ac131313@redhat.com>
> ppc Geoff Keating <geoffk@redhat.com>
> 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>
>
(NickC worded this very well)
I'm wondering if it would be helpful for sim specific maintainers (at
least for sim/common based sims) to have implicit approval/write
permission on the sim/common directory.
Which reminds me, Stephane Carrez should really be listed as the m68hc11
maintainer. Unless, that is, GDB is going to assume that a GDB target
maintainer implicitly maintains the corresponding SIM.
Thoughts?
Andrew
next reply other threads:[~2002-03-06 5:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 21:08 Andrew Cagney [this message]
2002-03-05 21:37 ` cgd
2002-03-07 15:08 ` Andrew Cagney
2002-03-23 13:23 ` Andrew Cagney
2002-03-25 7:12 ` Frank Ch. Eigler
2002-03-25 9:50 ` Andrew Cagney
2002-03-25 10:22 ` Frank Ch. Eigler
[not found] ` <mailpost.1017080577.5428@news-sj1-1>
2002-03-25 10:32 ` cgd
2002-03-25 10:49 ` Frank Ch. Eigler
2002-03-25 10:51 ` cgd
2002-03-25 10:53 ` Andrew Cagney
2002-03-12 9:31 ` Nick Clifton
2002-04-08 7:32 ` Ben Elliston
2002-04-08 9:42 ` Andrew Cagney
2002-04-09 5:57 ` Ben Elliston
[not found] ` <mailpost.1018357082.12343@news-sj1-1>
2002-04-09 11:05 ` cgd
2002-04-09 11:22 ` Ben Elliston
2002-04-09 12:32 ` 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=3C85A44B.6090403@cygnus.com \
--to=ac131313@cygnus.com \
--cc=ac131313@redhat.com \
--cc=bje@redhat.com \
--cc=cgd@broadcom.com \
--cc=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=geoffk@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