From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: Rsync over ssh (pulling from Cygwin to Linux) stalls..
Date: Mon, 14 Aug 2006 19:48:00 -0000 [thread overview]
Message-ID: <ebqk1d$fq0$1@sea.gmane.org> (raw)
In-Reply-To: <007201c6bfcc$29939810$a501a8c0@CAM.ARTIMI.COM>
Dave Korn wrote:
> On 14 August 2006 18:41, mwoehlke wrote:
>
>> Dave Korn wrote:
>>> On 14 August 2006 17:04, mwoehlke wrote:
>
>>>> My understanding is that if you place it in Public Domain, then anyone
>>>> can do anything with it and no one can stop this. IOW RedHat would be
>>>> safe because no one can prevent them from using Public Domain material
>>>> in any manner or fashion.
>>> That's not what "safe" means. If the program is in the public domain,
>>> rather than RH having the copyright assigned to them, then anyone could
>>> take it, make a proprietary version and distribute it without the sources,
>>> and RH would not be in a legal position to enforce the GPL on it because
>>> they would not be the copyright holder.
>> And the problem with this would be what, exactly? "Safe" in that no one
>> can take legal action against RH because of their use of it.
>
> No, redhat is "safe" in /that/ sense automatically, because the code is GPLd
> and so they and everyone else in the world can do what they like with it, and
> nobody can stop them. The meaning of "safe" for redhat would be "safe from
> anyone stealing it for proprietary use", because the code would not be safe
> against that unless someone who can afford lawyers - such as RH - holds the
> copyright.
...I think this is what Daryl is taking issue with: you are essentially
*forcing* GPL onto someone. Not everyone agrees with that philosophy (in
my case, it depends on my mood :-)).
--
Matthew
"We're all mad here. I'm mad. You're mad... You must be, or you wouldn't
have come here." -- The Cheshire Cat
next prev parent reply other threads:[~2006-08-14 19:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ebq6t1$hlt$2@sea.gmane.org>
[not found] ` <006401c6bfc0$da40e570$a501a8c0@CAM.ARTIMI.COM>
2006-08-14 17:45 ` mwoehlke
2006-08-14 17:54 ` mwoehlke
2006-08-14 18:02 ` Dave Korn
2006-08-14 18:05 ` Dave Korn
2006-08-14 19:48 ` mwoehlke [this message]
2006-08-15 0:02 ` Dave Korn
2006-08-15 15:48 ` mwoehlke
2006-08-16 13:23 ` Williams, Gerald S (Jerry)
2006-08-16 15:16 ` Christopher Faylor
2006-08-16 15:53 ` mwoehlke
2006-08-16 16:04 ` Corinna Vinschen
2006-08-16 16:17 ` Christopher Faylor
2006-08-16 16:54 ` mwoehlke
2006-08-17 16:31 ` Williams, Gerald S (Jerry)
2006-08-17 16:42 ` mwoehlke
2006-08-18 13:31 Williams, Gerald S (Jerry)
2006-08-18 14:17 ` Dave Korn
2006-08-18 14:26 ` mwoehlke
2006-08-18 14:44 ` Dave Korn
2006-08-18 15:09 ` mwoehlke
2006-08-18 15:45 ` Dave Korn
2006-08-18 15:58 ` mwoehlke
2006-08-18 16:06 ` Dave Korn
2006-08-18 16:42 ` Dave Korn
2006-08-18 18:28 ` Igor Peshansky
2006-08-18 14:43 ` Christopher Faylor
2006-08-18 16:34 ` Williams, Gerald S (Jerry)
2006-08-18 19:28 ` mwoehlke
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='ebqk1d$fq0$1@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@cygwin.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).