From: Robert Dewar <dewar@adacore.com>
To: Nicholas Mc Guire <hofrat@hofr.at>
Cc: Doug Evans <dje@google.com>,
Lokesh Gupta <lokesh.gupta@gmail.com>,
gdb@sourceware.org
Subject: Re: Tracepoints functionality for local targets
Date: Sun, 02 Mar 2008 11:37:00 -0000 [thread overview]
Message-ID: <47CA9144.6040209@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0803020048560.1951@vlab.hofr.at>
Nicholas Mc Guire wrote:
> It is GPL V2 and not assigned to the FSF - it was funded by Siemens AG
> (Cooperate Technology) and Im talking to them - but it took 1 year to
> get them to release it under the GPL and get permission to release it to
> the public so don't expect this to happen any time soon - anyway it is a
> supprise to me that it is insufficient to release code under the GPL V2
> and frankly if the FSF requires copyright assignment then this is bad news
> for free software developers
The FSF requires that people assign the copyright, this keeps the
copyright situation clear on the whole project. You have to be very
careful in copying code, just because someone somewhere says some
code is under the GPL does not make it so, you have to be 100% sure
that the person owning the copyright has issued the license, and the
way that FSF project does this is to insist on formal copyright
assignment. No one is compelled to do such an assignment of course,
but for the code to be part of the FSF GNU project, the FSF does
require this assignment.
> - what reason could I give any other company
> to require the same ?
The same reason that has convinced hundreds of individuals and
major corporations to assign code. If you assign the code to the
FSF, then it gets mainlined into the FSF development sources,
which means your patches are continuously tested, and you don't
have to deal with reinserting them in every new release.
If Siemens is interested in having this code be mainlined
into the GDB sources, they have to agree to the assignment.
If they are not interested in this, then they don't need
to agree, and unfortunately it won't happen.
> On the other hand if the FSF has legitimate reasons
> not to accept GPL code as it could lead to restrictions then this would
> be the case for any commercial entity as well and be really bad news for
> GPL all together.
It's is not a matter of restrictions, just a matter of being
careful about copyright and ownership. The GPL is not some magic
that removes this requirement for diligence.
> So I still hope that the GPL V2 code would be accepted
> by the GDB people.
There does need to be an assignment for it to be incorporated
next prev parent reply other threads:[~2008-03-02 11:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 10:03 Lokesh Gupta
2008-02-26 18:11 ` Daniel Jacobowitz
2008-02-26 18:39 ` Doug Evans
2008-03-01 19:29 ` Nicholas Mc Guire
2008-03-01 19:43 ` Doug Evans
2008-03-02 8:50 ` Nicholas Mc Guire
2008-03-02 11:37 ` Robert Dewar [this message]
2008-03-02 13:37 ` Nicholas Mc Guire
2008-03-02 14:00 ` Robert Dewar
2008-03-03 10:09 ` Richard Stallman
2008-03-03 19:54 ` Eli Zaretskii
2008-03-04 19:42 ` Richard Stallman
2008-02-27 1:06 ` Michael Snyder
2008-02-27 12:55 ` Lokesh Gupta
2008-02-27 22:00 ` Michael Snyder
2008-03-01 19:36 ` Nicholas Mc Guire
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=47CA9144.6040209@adacore.com \
--to=dewar@adacore.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=hofrat@hofr.at \
--cc=lokesh.gupta@gmail.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