From: fche@redhat.com (Frank Ch. Eigler)
To: Joachim Protze <joachim.protze@tu-dresden.de>
Cc: gdb@sourceware.org
Subject: Re: Licencing policy for gdb Python plugins
Date: Wed, 11 Jul 2012 21:34:00 -0000 [thread overview]
Message-ID: <y0mipdu6kyf.fsf@fche.csb> (raw)
In-Reply-To: <4FFC2F18.9000708@tu-dresden.de> (Joachim Protze's message of "Tue, 10 Jul 2012 15:33:12 +0200")
Joachim Protze <joachim.protze@tu-dresden.de> writes:
> [...] while the discussion in the last session of the GNU cauldron,
> the question raised, whether there is a licencing policy for Python
> plugins, [...]
Unless one believes the gdb plugin api is copyrightable in its own
right (and thus license compatibility comes up), perhaps discussion
should be limited to how the gdb project would accept said plugins as
a contribution.
- FChE
next prev parent reply other threads:[~2012-07-11 21:34 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
2012-07-11 12:18 ` Daniel Jacobowitz
2012-07-11 17:43 ` John Gilmore
2012-07-11 21:34 ` Frank Ch. Eigler [this message]
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=y0mipdu6kyf.fsf@fche.csb \
--to=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=joachim.protze@tu-dresden.de \
/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).