From: Florian Weimer <fw@deneb.enyo.de>
To: "Martin Schröder" <lionhead@onlinehome.de>
Cc: <gdb@sourceware.org>
Subject: Re: generic query regarding GPL and licensing terms associated with gdb
Date: Sun, 15 Aug 2010 16:40:00 -0000 [thread overview]
Message-ID: <87r5i0m3o7.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <A54F384137C64F4DBDD107B1B80886C5@igor> ("Martin =?iso-8859-1?Q?Schr=F6der=22's?= message of "Fri, 13 Aug 2010 17:35:11 +0200")
* Martin Schröder:
> As soon as the GPLed code itself is disclosed (see below for the only
> time when that is NOT the case), it can't technically contain any
> trade secrets.
This is not true at all. For instance, there is code under the GPL
which implements CSS, and it's publicly available, yet CSS is still a
trade secret.
next prev parent reply other threads:[~2010-08-15 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 4:08 paawan oza
2010-08-13 5:04 ` Robert Dewar
2010-08-13 6:16 ` paawan oza
2010-08-13 7:56 ` Martin Schröder
2010-08-13 14:26 ` Robert Dewar
2010-08-13 15:35 ` Martin Schröder
2010-08-13 16:18 ` Robert Dewar
2010-08-13 17:50 ` paawan oza
2010-08-13 18:15 ` Martin Schröder
2010-08-24 21:13 ` Steffen Dettmer
2010-08-24 21:33 ` Robert Dewar
2010-08-27 11:38 ` Steffen DETTMER
2010-08-15 16:40 ` Florian Weimer [this message]
2010-08-13 14:24 ` Robert Dewar
2010-08-13 15:50 ` Tom Tromey
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=87r5i0m3o7.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gdb@sourceware.org \
--cc=lionhead@onlinehome.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