From: Andrew Cagney <ac131313@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>, gdb@sources.redhat.com
Subject: Re: [maint] sim and common
Date: Mon, 25 Mar 2002 09:50:00 -0000 [thread overview]
Message-ID: <3C9F62F2.9000902@cygnus.com> (raw)
In-Reply-To: <20020325101111.A5475@redhat.com>
> Hi -
>
> On Sat, Mar 23, 2002 at 04:23:06PM -0500, Andrew Cagney wrote:
>
>> Did anyone else have a comment on this thread?
>>
>
>> > 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.
>> > [...]
>
>
> Whether it is helpful or not can be ascertained when/if such maintainers
> have patches for sim/common, and then if any "hindrance" in fact exists.
> Preemptively granting such permission, in the absence of a history/intent
> of specific contributions, goes against the grain of the rest of gdb.
If I understand the above correctly, your view is that, for the moment,
only BenE and yourself should approve changes to src/sim/common?
enjoy,
Andrew
next prev parent reply other threads:[~2002-03-25 17:50 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 [this message]
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=3C9F62F2.9000902@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cagney@redhat.com \
--cc=fche@redhat.com \
--cc=gdb@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