Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: cgd@broadcom.com, 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: Sat, 23 Mar 2002 13:23:00 -0000	[thread overview]
Message-ID: <3C9CF23A.5040306@cygnus.com> (raw)
In-Reply-To: <3C87F2DC.8070205@cygnus.com>

Did anyone else have a comment on this thread?

> 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-)
> 
> Sim directory maintenance was, for a long time, very vague.  I'm trying to clarify things a little so that people that have a motivation to work in this directory can do so with little or no hinderance.  At the same time trying to ensure that a few basic procedures are followed.
> 
> I think part of this is ensuring that people directly affected by the infrastructure have a fairly free reign over it.
> 
> Personally, I wouldn't mind someone else having responsibility for
> reviewing my 'common' patches.
> 
> Even if you have write privs on sim/common you're still free (encouraged?) to seek advice from others.  (Is this change a good idea?  In 20:20 hindsight was that bit a bad move?)
> 
> 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.
> 
> Just as long as the damage is limited to ``flesh wounds'' :-)  Whats the worst that could happen - something gets broken?  Oops!  Actually, I think that the worst that could happen is for the code's development to stagnate (unless, that is, there is no one that thinks it is useful).
> 
> enjoy,
> Andrew



  reply	other threads:[~2002-03-23 21:23 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 [this message]
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=3C9CF23A.5040306@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