From: "Frank Ch. Eigler" <fche@redhat.com>
To: Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
Cc: cgen@sources.redhat.com
Subject: Re: about copyright of m32r.cpu
Date: Fri, 13 Jun 2003 11:22:00 -0000 [thread overview]
Message-ID: <20030613112212.GC30985@redhat.com> (raw)
In-Reply-To: <015c01c3315a$d401a0c0$2569910a@hoku.renesas.com>
Hi -
On Fri, Jun 13, 2003 at 12:21:06PM +0900, Kazuhiro Inaoka wrote:
> I would like to change cgen/cpu.m32r.cpu and m32r.opc.
> The file is proprietary to Red Hat.
> Would I send patches?
You are welcome to send patches. These patches would likely
carry your own copyright into these files. Since the m32r
port is used in binutils and gdb(sim), the generated files are
automatically assigned to the FSF, it's necessary that you have
active FSF copyright assignments for binutils and gdb.
- FChE
prev parent reply other threads:[~2003-06-13 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 3:19 Kazuhiro Inaoka
2003-06-13 11:22 ` Frank Ch. Eigler [this message]
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=20030613112212.GC30985@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=inaoka.kazuhiro@renesas.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).