public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	Andrew Cagney <cagney@redhat.com>,
	binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: [rfa] FRV input files
Date: Wed, 07 May 2003 16:20:00 -0000	[thread overview]
Message-ID: <16057.12829.240057.205613@casey.transmeta.com> (raw)
In-Reply-To: <3EB82C29.2050201@redhat.com>

Andrew Cagney writes:
 > > (C)FSF?  And what does this have to do with your improvised license
 > > change?
 > 
 > What "improvised license change"?

Uh, do a diff between your submitted frv.cpu and src/cgen/cpu/frv.cpu.
["I did, and src/cgen/cpu/frv.cpu is copyright Redhat!"
"Uh, I'm refering to the copyright terms."]

Also, I'm not sure I want *.cpu to say it's part of Binutils.
I might very well want to make a cgen release all by itself,
and I'd like to maintain the separation between cgen and its
clients.  Binutils is just another client of cgen.
A minor point, but early warning that I'll probably make the change
at some point.
["But cgen isn't copyright FSF."
"Doesn't mean some version can't be."]


1,4c1,21
< ; Fujitsu FRV CPU description.  -*- Scheme -*-
< ; Copyright (C) 2000, 2001 Red Hat, Inc.
< ; This file is part of CGEN.
< ; See file COPYING.CGEN for details.
---
> ; Fujitsu FRV opcode support, for GNU Binutils.  -*- Scheme -*-
> ;
> ; Copyright 2003 Free Software Foundation, Inc.
> ;
> ; Contributed by Red Hat Inc; developed under contract from Fujitsu.
> ;
> ; This file is part of the GNU Binutils.
> ;
> ; This program is free software; you can redistribute it and/or modify
> ; it under the terms of the GNU General Public License as published by
> ; the Free Software Foundation; either version 2 of the License, or
> ; (at your option) any later version.
> ;
> ; This program is distributed in the hope that it will be useful,
> ; but WITHOUT ANY WARRANTY; without even the implied warranty of
> ; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> ; GNU General Public License for more details.
> ;
> ; You should have received a copy of the GNU General Public License
> ; along with this program; if not, write to the Free Software
> ; Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

  reply	other threads:[~2003-05-07 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3EB31259.8050603@redhat.com>
2003-05-03  1:07 ` Doug Evans
2003-05-03  1:10   ` Doug Evans
     [not found]   ` <3EB40A72.1060304@redhat.com>
2003-05-03 20:37     ` Doug Evans
     [not found]       ` <3EB43D55.7000508@redhat.com>
2003-05-03 23:21         ` Doug Evans
2003-05-04 11:27         ` Frank Ch. Eigler
2003-05-04 15:13           ` Andrew Cagney
2003-05-05 13:36             ` Frank Ch. Eigler
2003-05-06 21:42               ` Andrew Cagney
2003-05-07 16:20                 ` Doug Evans [this message]
2003-05-07 18:34                   ` Andrew Cagney
2003-05-07 19:19                     ` Doug Evans
2003-05-07 19:46                       ` Andrew Cagney
2003-05-07 19:56                       ` 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=16057.12829.240057.205613@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=cagney@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@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).