From: Andrew Cagney <ac131313@cygnus.com>
To: Ben Elliston <bje@redhat.com>
Cc: Nick Clifton <nickc@redhat.com>,
Andrew Cagney <ac131313@redhat.com>,
Geoff Keating <geoffk@redhat.com>,
Chris Demetriou <cgd@broadcom.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
gdb@sources.redhat.com
Subject: Re: [maint] sim and common
Date: Mon, 08 Apr 2002 09:42:00 -0000 [thread overview]
Message-ID: <3CB1C857.9080902@cygnus.com> (raw)
In-Reply-To: <15537.43529.140988.838892@toenail.toronto.redhat.com>
> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
>
>
> Andrew> I'm wondering if it would be helpful for sim specific
> Andrew> maintainers (at least for sim/common based sims) to have
> Andrew> implicit approval/write permission on the sim/common
> Andrew> directory.
>
> Why do you feel it would be helpful? I don't think there has been any
> evidence that patch approvals for sim/common has been a bottleneck or
> indeed even a problem for anyone to date.
Is it unhelpful? The people with the best idea for what to do with the
common framework are most likely going to be those that are actively
developing simulators. Right now that is CGD (Chris D).
Anyway, further down in the thread, Frank has stated that, in his
opinion, GDB's global write maintainers have ``global write'' on
sim/common. Is this what you understand?
(Unless otherwise stated, global-write stops when there is a maintainer).
> Andrew> Which reminds me, Stephane Carrez should really be listed as
> Andrew> the m68hc11 maintainer. Unless, that is, GDB is going to
> Andrew> assume that a GDB target maintainer implicitly maintains the
> Andrew> corresponding SIM.
>
> I'm happy enough with that idea, provided that there is a mechanism
> for people to be listed explicitly as sim maintainers, overriding the
> corresponding GDB maintainer for that port.
GDB's isa/abi, native, host and sim maintainers are recognized as
separate independant roles (but are sometimes the same person).
The above was a suggestion for how to handle the situtation where the
SIM role is vacent. I think the consensus is that the SIM maintainers
should be identified separatly and explicitly.
> There are potential sim
> maintainers who are capable of working on the sim but might not be
> willing/able to work on GDB as well.
I don't understand. Perhaphs you're thinking of a situtation like
sim/arm/ or sim/ppc/. There are two roles: GDB's sim maintainer (NickC,
Cagney/GeoffK); and (independant of GDB) the original
developers/contributors (Arm Ltd?, Cagney). (Yes, again, they can be the
same person).
enjoy,
Andrew
next prev parent reply other threads:[~2002-04-08 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 21:08 Andrew Cagney
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 [this message]
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=3CB1C857.9080902@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