public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: binutils@sources.redhat.com, cgen@sources.redhat.com,
	sid@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: New Sanyo Stormy16 relocations
Date: Wed, 18 Dec 2002 07:47:00 -0000	[thread overview]
Message-ID: <o5el8f1g8f.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <3E004FDF.3060304@redhat.com>


cagney wrote:

> [...]
> > Cgen folks (and others)...  would it be acceptable to change the cgen
> > approval rules to allow people who could otherwise approve
> > port-specific patches in binutils, gdb, or sid, to be allowed to
> > approve port-specific changes in cgen as well?
> 
> This would only all make sense if the .opc et.al. files were all (C)
> FSF.  [...]

Sorry, I don't see how that relates to the issue.  Regardless of whose
(C) is on the files, the current matter is which of several potential
maintainer types should feel free to commit changes.


- FChE

  reply	other threads:[~2002-12-18 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1039041358.28757.307.camel@p4>
     [not found] ` <20021204225643.GS27956@bubble.sa.bigpond.net.au>
     [not found]   ` <1039043233.28767.313.camel@p4>
2002-12-16 19:53     ` DJ Delorie
2002-12-16 20:30       ` Alan Modra
2002-12-16 20:48         ` DJ Delorie
2002-12-17 11:25       ` Doug Evans
2002-12-17 11:47         ` DJ Delorie
2002-12-17 11:56           ` Frank Ch. Eigler
2002-12-17 12:09           ` Doug Evans
2002-12-17 12:14             ` Doug Evans
2002-12-18  2:37           ` Andrew Cagney
2002-12-18  7:47             ` Frank Ch. Eigler [this message]
2002-12-17 14:39         ` Ben Elliston

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=o5el8f1g8f.fsf@toenail.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).