Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: cgd@broadcom.com
To: "Andrew Cagney" <ac131313@cygnus.com>
Cc: "Nick Clifton" <nickc@redhat.com>,
	"Andrew Cagney" <ac131313@redhat.com>,
	"Geoff Keating" <geoffk@redhat.com>,
	"Ben Elliston" <bje@redhat.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	gdb@sources.redhat.com
Subject: Re: [maint] sim and common
Date: Tue, 05 Mar 2002 21:37:00 -0000	[thread overview]
Message-ID: <yov57koq1ck0.fsf@broadcom.com> (raw)
In-Reply-To: "Andrew Cagney"'s message of "Wed, 06 Mar 2002 00:08:27 -0500"

At Wed, 06 Mar 2002 00:08:27 -0500, Andrew Cagney wrote:
> 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.

Uh, I was assuming that in general we (sim maintainers) had write
after approval perms, but that approval was still required.
(Concerned by your "write permission" comment there.  Do tell me if
i'm wrong.  8-)


Personally, I wouldn't mind someone else having responsibility for
reviewing my 'common' patches.

I'd like to make sure i'm not doing more damage than i intend, and i
say 'responsibility' because if somebody doesn't consider it their
responsibility well, then, it probably won't happen.

Of course, I'm sure we all have more than enough work to do...


My hope is to get approval, and hopefully consensus, for a bunch of
common patches over the next couple of months.  To "minor" things
like, oh, making the trace format a lot less lame.  8-)



chris


  reply	other threads:[~2002-03-06  5:37 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 [this message]
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=yov57koq1ck0.fsf@broadcom.com \
    --to=cgd@broadcom.com \
    --cc=ac131313@cygnus.com \
    --cc=ac131313@redhat.com \
    --cc=bje@redhat.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