From: Robin Getz <rgetz@blackfin.uclinux.org>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Mike Frysinger <vapier@gentoo.org>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: libsim licensing (and bfd by extension)
Date: Fri, 07 May 2010 19:39:00 -0000 [thread overview]
Message-ID: <201005071539.03142.rgetz@blackfin.uclinux.org> (raw)
In-Reply-To: <20100507182547.GV8410@caradoc.them.org>
On Fri 7 May 2010 14:25, Daniel Jacobowitz pondered:
> On Fri, May 07, 2010 at 02:24:25PM -0400, Robin Getz wrote:
> > On Tue 4 May 2010 23:12, Daniel Jacobowitz pondered:
> > > Also bits of sim are copyright others besides the FSF.
> >
> > I didn't think that was possible?
> >
> > (but - as you state - I do see lots of copyright ARM, Cygnus Solutions,
> > Sun Microsystems, European Space Agency, etc in the sim sources).
> >
> > Doesn't the sim require a copyright assignment to the FSF (like the
> > rest of the gdb/binutils does?)
>
> We'd like it to, but some things were not assigned to the FSF when
> they were originally contributed. Beyond that, I don't know the
> history.
It's easy to remove them now. :)
If people want it to be added back - it's easy for them to sign the proper
forms.
I admit - a little Draconian - but it would get it to where you wanted it to
be.
Besides - some of the files which are not copyright FSF - aren't released
under the "GPL 2 or later"...
common/cgen-fpu.h
common/cgen-accfp.c
common/cgen-fpu.c
That needs to be fixed/resolved - doesn't it?
next prev parent reply other threads:[~2010-05-07 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 23:52 Mike Frysinger
2010-05-05 3:12 ` Daniel Jacobowitz
2010-05-05 5:04 ` Mike Frysinger
2010-05-07 18:24 ` Robin Getz
2010-05-07 18:25 ` Daniel Jacobowitz
2010-05-07 19:39 ` Robin Getz [this message]
[not found] ` <201005071539.03142.rgetz__26985.0316843533$1273261162$gmane$org@blackfin.uclinux.org>
2010-05-08 16:54 ` 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=201005071539.03142.rgetz@blackfin.uclinux.org \
--to=rgetz@blackfin.uclinux.org \
--cc=binutils@sourceware.org \
--cc=dan@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.org \
/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