From: Daniel Jacobowitz <drow@mvista.com>
To: Fred Viles <fv@epitools.com>
Cc: gdb@sources.redhat.com
Subject: Re: libremote status?
Date: Thu, 10 Oct 2002 19:30:00 -0000 [thread overview]
Message-ID: <20021011023049.GA8352@nevyn.them.org> (raw)
In-Reply-To: <3DA5D2A0.6277.13A0987@localhost>
On Thu, Oct 10, 2002 at 07:18:56PM -0700, Fred Viles wrote:
> Dang, bitten by the listserver (and my inattention) again. Sorry for
> the PM, Chris.
>
> ------- Forwarded message follows -------
> From: Fred Viles <fv@epitools.com>
> To: Christopher Faylor <cgf@redhat.com>
> Subject: Re: libremote status?
> Date sent: Thu, 10 Oct 2002 19:17:07 -0700
>
> On 9 Oct 2002 at 15:03, Christopher Faylor wrote about
> "Re: libremote status?":
>
> | On Wed, Oct 09, 2002 at 02:42:35PM -0400, Daniel Jacobowitz wrote:
> | >On Wed, Oct 09, 2002 at 09:39:53AM -0700, Kevin Buettner wrote:
> | >I assume that, given the name change, there is no plan for RDA to be
> | >contributed to the FSF? And that, as such, there can be no effort to
> | >combine all this beautiful server architecture with the fact that we
> | >have a working gdbserver implementation, and active development on it?
> |
> | We will not be releasing this to the FSF, no. We still need to hold
> | the copyright for various reasons.
>
> OTOH, according to the comment blocks at the start of every file you
> are releasing it under the GPL. Doesn't that mean that it can be
> incorporated into other GPL'ed projects pretty much without
> additional restriction? I obviously son't understand the issues
> here...
In general, yes; GNU projects, no. Remember the oft-mentioned
copyright assignment forms? It's FSF policy (usually) that the FSF
hold copyright on the entire source base of a GNU project like GDB.
It's a reasonable policy; it gives the FSF close control over licensing
issues and centralizes copyright defense if it should become necessary.
I believe those are the reasons.
[And I want to apologize again to Chris and others for my tone in that
quote; I do really appreciate the work they've done to get this project
released to the community.]
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-11 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 19:19 Fred Viles
2002-10-10 19:30 ` Daniel Jacobowitz [this message]
2002-10-18 16:34 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 18:33 Fred Viles
2002-07-13 10:05 ` Christopher Faylor
2002-07-13 23:20 ` Fred Viles
2002-10-08 20:42 ` Fred Viles
2002-10-09 9:40 ` Kevin Buettner
2002-10-09 11:41 ` Daniel Jacobowitz
2002-10-09 12:01 ` Christopher Faylor
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=20021011023049.GA8352@nevyn.them.org \
--to=drow@mvista.com \
--cc=fv@epitools.com \
--cc=gdb@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