From: Per Bothner <per@bothner.com>
To: Quality Quorum <qqi@world.std.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: Where is GDB going
Date: Sun, 25 Feb 2001 23:41:00 -0000 [thread overview]
Message-ID: <m27l2d51cm.fsf@kelso.bothner.com> (raw)
In-Reply-To: <Pine.SGI.4.21.0102260005570.18201-100000@world.std.com>
Quality Quorum <qqi@world.std.com> writes:
> I agree that there should be a line in the sand, however, currently
> it is way far to the left. If people have intellectual property and
> trade secrets hardwired into their hardware, then they should be allowed
> to protect these secrets from disclosure by writing closed library
> obscuring details of their stuff.
Of course they should be. RMS would agree 100%. But you're missing
the point: if people make that choice, they have no right to expect a
free ride from Free Software. What does Free Software (or the World
for that matter) gain by making it too easy for people to keep their
intellectual property secret? The whole point of GNU to encourage
openness, not trade secrets.
Anyway, discussion about the morality of the GPL are not appropriate
to this mailing list. Concrete questions about the licensing
implications of using Gdb remote stubs, probably ok, I guess.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
next prev parent reply other threads:[~2001-02-25 23:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 13:52 Andrew Cagney
2001-02-23 14:21 ` Quality Quorum
2001-02-25 15:48 ` Steven Johnson
2001-02-25 21:15 ` Quality Quorum
2001-02-25 23:41 ` Per Bothner [this message]
2001-02-26 9:39 ` Quality Quorum
2001-02-26 10:02 ` correction. " Quality Quorum
2001-02-26 13:45 ` Per Bothner
2001-02-26 16:29 ` Quality Quorum
2001-02-26 13:53 ` Steven Johnson
2001-02-25 18:11 Peter Reilley
2001-02-25 20:52 ` Steven Johnson
2001-02-25 21:22 ` Quality Quorum
2001-02-26 20:34 Peter Reilley
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=m27l2d51cm.fsf@kelso.bothner.com \
--to=per@bothner.com \
--cc=gdb@sources.redhat.com \
--cc=qqi@world.std.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).