Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: <dj_barrow@ariasoft.ie>, 	<gdb@sourceware.org>
Subject: RE: how to get uptodate vxworks gdb source code
Date: Thu, 02 Mar 2006 15:41:00 -0000	[thread overview]
Message-ID: <037d01c63e0f$c3000db0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060302153123.51251.qmail@web51109.mail.yahoo.com>

On 02 March 2006 15:31, D.J. Barrow wrote:

> Hi Dave,
> From my understanding of GPL they have to make the sources freely
> available to everyone, the licence is supposed to be infectious

  Your understanding is seriously wrong, and the bit about 'infectious' is a
bit of dark propaganda made up by opponents of the GPL.  The GPL is as I
described it in my last post: *if* you distribute, in any fashion, a binary
version of a GPL'd program to someone, *then* you must also supply, or offer
to supply, to that same someone, the exact sources from which that binary was
built.  You have no obligations to anyone you do not distribute binaries to.

> Gnu wouldn't neuter this licence.

  They haven't done, you've misunderstood its intent.  You now need to take
two steps:

#1.  Take this discussion to one of the gpl discussion lists, as it no longer
has any relevance to GDB.
#2.  Go read the GPL FAQ at http://www.gnu.org/licenses/gpl-faq.html, it
should clarify your understanding of the rights and obligations under the GPL.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


  parent reply	other threads:[~2006-03-02 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 12:00 D.J. Barrow
2006-03-02 13:43 ` Dave Korn
2006-03-02 15:31   ` D.J. Barrow
2006-03-02 15:34     ` Daniel Jacobowitz
2006-03-02 15:41     ` Dave Korn [this message]
2006-03-02 17:43     ` Joel Brobecker

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='037d01c63e0f$c3000db0$a501a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=dj_barrow@ariasoft.ie \
    --cc=gdb@sourceware.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