From: Stan Shebs <stanshebs@earthlink.net>
To: gdb@sourceware.org
Subject: Re: Licencing policy for gdb Python plugins
Date: Tue, 10 Jul 2012 14:19:00 -0000 [thread overview]
Message-ID: <4FFC39B3.70505@earthlink.net> (raw)
In-Reply-To: <4FFC2F18.9000708@tu-dresden.de>
On 7/10/12 3:33 PM, Joachim Protze wrote:
> Hi,
>
> while the discussion in the last session of the GNU cauldron, the
> question raised, whether there is a licencing policy for Python plugins,
> as there is a quite strict policy for gcc plugins. As no one in the
> audience had an opinion to this question, I think the gdb developers
> attended the other track. Searching the wiki, the mailinglist and the
> web I did not find any hints for a policy. Is there any policy or
> recommendation?
>
Sorry, some of us were off in a different room and didn't notice the time!
In any case, I don't recall much thought about a GDB plugin licensing
policy, but I imagine there would have to be a pretty strong rationale
for it to differ from the GCC policy.
Stan Shebs
stan@codesourcery.com
next prev parent reply other threads:[~2012-07-10 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 13:33 Joachim Protze
2012-07-10 14:19 ` Stan Shebs [this message]
2012-07-11 12:18 ` Daniel Jacobowitz
2012-07-11 17:43 ` John Gilmore
2012-07-11 21:34 ` Frank Ch. Eigler
2012-07-11 21:52 ` Doug Evans
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=4FFC39B3.70505@earthlink.net \
--to=stanshebs@earthlink.net \
--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