From: Piet/Pete Delaney <piet@sgi.com>
To: Salman Khilji <salmankhilji@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Questions for GDB Developers
Date: Fri, 25 Jan 2002 19:21:00 -0000 [thread overview]
Message-ID: <20020125192127.B66623@sgi.com> (raw)
In-Reply-To: <F1203Vp20N39x6HHGNZ000179c9@hotmail.com>
On Sat, Jan 26, 2002 at 03:12:35AM +0000, Salman Khilji wrote:
> I did a little reading on the licensing and yes it does seem that lifting
> the code and creating a proprietory "real-time data monitor" would be
> against the licensing.
Why do you think that? I've been of the impression that you can't take
even part of the code. I don't even know if you can call binutils without
the code having to be copyleft. I recall hearing of other programs having
to remove calls to GNU libraries just to stay out of the copyleft restristions.
I would think it even in the spirit of the GNU license that anything intended
to bolt into gdb, like ddd or a stub should also have to be covered by these
concepts. Isn't the idea to build a free and open software environment?
-piet
next prev parent reply other threads:[~2002-01-26 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 19:12 Salman Khilji
2002-01-25 19:21 ` Piet/Pete Delaney [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-25 4:53 Salman Khilji
2002-01-25 14:41 ` Stan Shebs
2002-01-31 12:34 ` Michael Snyder
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=20020125192127.B66623@sgi.com \
--to=piet@sgi.com \
--cc=gdb@sources.redhat.com \
--cc=salmankhilji@hotmail.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