From: "Frank Ch. Eigler" <fche@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: Committed: src/cpu/cris.cpu, intended for src/sim/ src/sid/component/cgen-cpu/ but some problems
Date: Fri, 03 Dec 2004 04:42:00 -0000 [thread overview]
Message-ID: <20041203044228.GM15612@redhat.com> (raw)
In-Reply-To: <200412030208.iB328DUr015412@ignucius.se.axis.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hi -
> > Plus sid is not as well known, and some people have expressed
> > reservations about Red Hat retaining its copyright over the
> > core of the software.
>
> BTW, we'll have to resolve the copyright issue for the CRISv32
> sid port and assorted components to be merged. [...]
> Is there a defined path for contributing to SID without copyright
> assignment to Red Hat? Can this be solved?
We have been taking contributions to sid and cgen without formal
copyright assignment: your copyright would just get added to
the list. CGEN needs to be modified to be taught this, to avoid
the rubber-stamping of "Copyright (C) Red Hat" in sid-bound
generated files.
> (I thought such a
> path was in progress of being defined a year ago or so, or sid
> copyright assigned to the FSF or suchlike.) [...]
That was for eCos, a process which sadly appears stalled.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-12-03 4:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 12:03 Hans-Peter Nilsson
2004-12-03 0:46 ` Frank Ch. Eigler
2004-12-03 2:08 ` Hans-Peter Nilsson
2004-12-03 4:42 ` 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=20041203044228.GM15612@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=hans-peter.nilsson@axis.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).