Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: Andrew Cagney <ac131313@cygnus.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: Tue, 09 Apr 2002 05:57:00 -0000	[thread overview]
Message-ID: <15538.58681.963609.704984@toenail.toronto.redhat.com> (raw)
In-Reply-To: <3CB1C857.9080902@cygnus.com>

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:

  >> 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.

  Andrew> Is it unhelpful?  The people with the best idea for what to do with the 
  Andrew> common framework are most likely going to be those that are actively 
  Andrew> developing simulators.   Right now that is CGD (Chris D).

While I agree with this point, I also like the idea of having a
devil's advocate to approve sim/common patches.  In the heat of the
moment, it's easy to think of patches to sim/common to solve
port-specific problems that are not in the best interest of all
simulators.

  Andrew> Anyway, further down in the thread, Frank has stated that,
  Andrew> in his opinion, GDB's global write maintainers have ``global
  Andrew> write'' on sim/common.  Is this what you understand?

I had not seen that, but okay.

  Andrew> The above was a suggestion for how to handle the situtation
  Andrew> where the SIM role is vacent.  I think the consensus is that
  Andrew> the SIM maintainers should be identified separatly and
  Andrew> explicitly.

Good.

Ben


  reply	other threads:[~2002-04-09 12:57 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
2002-04-09  5:57     ` Ben Elliston [this message]
     [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=15538.58681.963609.704984@toenail.toronto.redhat.com \
    --to=bje@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=ac131313@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