Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: cgd@broadcom.com
To: "Andrew Cagney" <ac131313@cygnus.com>
Cc: cagney@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] sim/MAINTAINERS clarifications.
Date: Thu, 07 Mar 2002 15:57:00 -0000	[thread overview]
Message-ID: <yov5lmd4exsj.fsf@broadcom.com> (raw)
In-Reply-To: "Andrew Cagney"'s message of "Thu, 07 Mar 2002 17:01:55 -0500"

At Thu, 07 Mar 2002 17:01:55 -0500, Andrew Cagney wrote:
> > +common, igen	Ben Elliston <bje@redhat.com>
> > +		Frank Ch. Eigler <fche@redhat.com>
> 
> I think igen maintenance is better left to the people that need to hack 
> on it - mips (ppc if I finished hacking it), mn10300, v850, d10v, d30v, 
> ??? maintainers.

actually, looks like currently only:

	mips
	mn10300
	tic80
	v850
	d30v		(mmm, preprocessed by m4!)

use igen.  (i.e., from your list, _not_ d10v.  It uses gencode on
d10v-opc.c, it seems.)

So, anyway, how about the change below?

(If you're prefer to keep things "loose" and relatively un-specified
as they are now, that's fine w/ me, but i figure, hey if this is
the hoped-for policy why not document?  8-)



chris
===================================================================
[ sim/ChangeLog ]
2002-03-07  Chris Demetriou  <cgd@broadcom.com>

	* MAINTAINERS: Tweak spacing.  Note the following:
	write-after-approval and obvious fix policies, "igen" is
	maintained by the maintainers of the sims that use it,
	"testsuite" bits for particular sims are maintained by
	those sims' maintainers.

Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/sim/MAINTAINERS,v
retrieving revision 1.9
diff -u -r1.9 MAINTAINERS
--- MAINTAINERS	2002/03/06 20:15:53	1.9
+++ MAINTAINERS	2002/03/07 23:54:27
@@ -1,19 +1,35 @@
-		SIM Maintainers
+			   SIM Maintainers
 
 The simulator is part of the GDB project, so see the file
 gdb/MAINTAINERS for general information about maintaining these files.
+(In particular, the same obvious fix and write after approval rules
+apply here.)
 
 If you are considering contributing a patch, please see the file
 gdb/CONTRIBUTE.  Patches to these files should be posted to:
 gdb-patches@sources.redhat.com 
+
 	
-	Maintainers for particular sims:
+Maintainers for particular sims:
 
 arm	        Nick Clifton <nickc@redhat.com>
+
 ppc		Andrew Cagney <ac131313@redhat.com>
-ppc		Geoff Keating <geoffk@redhat.com>
+		Geoff Keating <geoffk@redhat.com>
+
 m68hc11		Stephane Carrez <Stephane.Carrez@worldnet.fr>
+
 mips		Andrew Cagney <ac131313@redhat.com>
-mips		Chris Demetriou <cgd@broadcom.com>
+		Chris Demetriou <cgd@broadcom.com>
+
+
+Maintainers for other subdirectories:
+
 common		Ben Elliston <bje@redhat.com>
-common		Frank Ch. Eigler <fche@redhat.com>
+		Frank Ch. Eigler <fche@redhat.com>
+
+igen		Maintainers for sims that use it.  Currently used
+		by: d30v, mips, mn10300, tic80 v850.
+
+testsuite	Sim maintainers are the maintainers of the directories
+		which correspond to their sims.


  reply	other threads:[~2002-03-07 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 12:26 cgd
2002-03-07 14:02 ` Andrew Cagney
2002-03-07 15:57   ` cgd [this message]
2002-03-07 14:23 ` Andrew Cagney
2002-03-07 18:12 ` 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=yov5lmd4exsj.fsf@broadcom.com \
    --to=cgd@broadcom.com \
    --cc=ac131313@cygnus.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@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