From: Stan Shebs <shebs@cygnus.com>
To: bartv@cygnus.co.uk
Cc: ecos-discuss@cygnus.com
Subject: Re: [ECOS] Re: CPU Ports for eCos
Date: Wed, 28 Apr 1999 12:17:00 -0000 [thread overview]
Message-ID: <199904281917.MAA16164@andros.cygnus.com> (raw)
In-Reply-To: <199904281847.TAA16399@sheesh.cygnus.co.uk>
Date: Wed, 28 Apr 1999 19:47:41 +0100
From: Bart Veer <bartv@cygnus.co.uk>
For those changes to get accepted into the main sources, a copyright
assignment is needed. The author of any non-trivial changes has to
assign all rights to those changes to the FSF, thus avoiding any
confusion about who owns which bits of the compiler. The GPL does not
impose any obligations in this area, it is a voluntary step, but in
most cases it is worth doing to avoid the merging problems.
Just to amplify on Bart's valuable comments, this is just a policy of
the FSF, but it's followed pretty strictly. From time to time people
offer me pieces of code for GDB that still have somebody else's
copyright on them! This would certainly lead to a unpleasant legal
imbroglio, if we were to incorporate them in GNU code. So the rule
is: no assignment, no incorporation.
Stan
next prev parent reply other threads:[~1999-04-28 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 13:41 [ECOS] " Nelson, Charles
1999-04-26 6:50 ` [ECOS] " Bart Veer
1999-04-28 6:41 ` Fernando D. Mato Mira
1999-04-28 7:10 ` Bart Veer
1999-04-28 8:52 ` Fernando D. Mato Mira
1999-04-28 11:48 ` Bart Veer
1999-04-28 12:17 ` Stan Shebs [this message]
1999-04-27 14:02 alex
1999-04-28 4:17 ` Bart Veer
1999-04-28 8:00 ` Jonathan Larmour
1999-04-28 12:04 ` Ian Lance Taylor
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=199904281917.MAA16164@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=bartv@cygnus.co.uk \
--cc=ecos-discuss@cygnus.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).