From: Dave Brolley <brolley@redhat.com>
To: Joern Rennecke <joernr@arc.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, cgen@sources.redhat.com
Subject: Re: copyright issues for cgen-generated tools
Date: Tue, 16 Jan 2007 15:01:00 -0000 [thread overview]
Message-ID: <45ACE8C8.3040700@redhat.com> (raw)
In-Reply-To: <20070116132856.GA27599@elsdt-razorfish.arc.com>
Joern Rennecke wrote:
>That might be descriptive of m32r.cpu, but when you look at sh64-compact.cpu,
>the difference between the cpu/ and the cgen/cpu/ versions is larger than
>the cpu/ version. Also, the cgen/cpu/ version has only Red Hat copyright
>notices, for 2000 and 2006; the cpu/ version has only a 2000 copyright
>notice.
>The old/new code ratio is even worse for sh.cpu
>
>There are also significantly more files in cgen/cpu than in cpu/ ;
>the difference are new additions, leading strength to the impression
>that cgen/cpu/ is the master copy.
>
>
We recently completed work to implement the entire sh architecture in
SID starting with the existing sh64 implementation which already existed
in cpu/ and cgen/cpu and which were nearly identical at the time. No one
could tell me which one was the master and it appeared that some work
was in cgen/cpu/ but not in cpu/, so I arbitrarily chose to work in
cgen/cpu/.
It doesn't matter to us (Red Hat) where the copyright lies for this
port, so feel free to bring cpu/ up to date and make it the master if
you please.
Dave
next prev parent reply other threads:[~2007-01-16 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 11:38 Joern Rennecke
2007-01-15 19:39 ` Frank Ch. Eigler
2007-01-16 13:31 ` Joern Rennecke
2007-01-16 15:01 ` Dave Brolley [this message]
2007-01-16 19:29 ` Frank Ch. Eigler
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=45ACE8C8.3040700@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.com \
--cc=joernr@arc.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).