From: Joel Brobecker <brobecker@adacore.com>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Work on the SIS ERC32 Emulator
Date: Wed, 20 Apr 2011 16:19:00 -0000 [thread overview]
Message-ID: <20110420161910.GN21392@adacore.com> (raw)
In-Reply-To: <8762qbseb0.fsf@gnu.org>
> Ok. I though the policy was different for the sims, since they are full
> of non-FSF copyrighted code. All right, I have to talk with my Employer
> about this. I am pretty familiar with the copyright assignment process
> with the FSF, but my Employer is not and it may take some time.
We failed to follow the normal guidelines, and I've heard the reason
for that in some of the cases, but that was a long time ago. IMO,
that was a mistake, for several reasons I don't want to detail here.
However, as you have noticed, because the FSF is not the copyright
holder of some of the files, we couldn't update the license to GPLv3.
> Do you plan to upgrade the files under 'sis' from GPLv2+ to GPLv3+?
I only see 2 "sis" files: erc32/sis.[hc]. Are these the files you
are referring to? I don't know how "easy" it's going to be doing
that upgrade, since the FSF does not hold the copyright to these
files. I don't think we can upgrade the license on our own, can we?
--
Joel
next prev parent reply other threads:[~2011-04-20 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 12:20 Jose E. Marchesi
2011-04-18 12:32 ` Tristan Gingold
2011-04-18 13:03 ` Jose E. Marchesi
2011-04-18 16:33 ` Joel Brobecker
2011-04-18 16:46 ` Jose E. Marchesi
2011-04-20 16:19 ` Joel Brobecker [this message]
2011-04-20 16:33 ` Ralf Corsepius
2011-04-21 20:45 ` Joel Brobecker
2011-04-22 10:30 ` Jose E. Marchesi
2011-04-20 16:38 ` Joel Sherrill
2011-04-20 16:43 ` Joel Brobecker
2011-04-20 16:47 ` Joel Brobecker
2011-04-20 16:57 ` Jose E. Marchesi
[not found] <00b301cc0366$9b4e76e0$d1eb64a0$@inpe.br>
2011-04-25 16:50 ` Jose E. Marchesi
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=20110420161910.GN21392@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jemarch@gnu.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