From: Christopher Faylor <me@cgf.cx>
To: Steven Johnson <sjohnson@sakuraindustries.com>,
insight@sources.redhat.com
Subject: Re: Insight and Licencing of TCL/TK Code
Date: Mon, 16 May 2005 16:12:00 -0000 [thread overview]
Message-ID: <20050516161058.GJ15318@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4289E11D.8050803@sakuraindustries.com>
On Tue, May 17, 2005 at 01:18:37AM -1100, Steven Johnson wrote:
>I also noticed this issue seems limited to the TCL/TK portions of
>insight, i havent noticed any Redhat copyrights in the C code that
>interfaces the core of GDB with the TCL/TK Code.
So, since Red Hat doesn't care, we can just start accepting patches for
insight from people who already have gdb assignments with the FSF.
Then, if/when insight is assigned to the FSF there won't be any issues
with the code.
cgf
next prev parent reply other threads:[~2005-05-16 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 22:13 Current Status of Insight Paul Schlie
2005-05-16 5:35 ` Steven Johnson
2005-05-16 13:18 ` Insight and Licencing of TCL/TK Code Steven Johnson
2005-05-16 13:31 ` Duane Ellis
2005-05-16 13:39 ` Jon Beniston
2005-05-16 14:15 ` Steven Johnson
2005-05-16 16:12 ` Christopher Faylor [this message]
2005-05-17 19:33 ` Current Status of Insight Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18 ` Paul Schlie
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=20050516161058.GJ15318@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=insight@sources.redhat.com \
--cc=sjohnson@sakuraindustries.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).