public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'TGI The Cygwin-Talk Maiming List'" <cygwin-talk@cygwin.com>
Subject: RE: Rsync over ssh (pulling from Cygwin to Linux) stalls..
Date: Fri, 18 Aug 2006 15:45:00 -0000	[thread overview]
Message-ID: <011501c6c2dd$5edfbd00$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <ec4l54$9aq$1@sea.gmane.org>

On 18 August 2006 16:08, mwoehlke wrote:

> Dave Korn wrote:
>> On 18 August 2006 15:26, mwoehlke wrote:
>>> Dave Korn wrote:
>>>> On 18 August 2006 14:31, Williams, Gerald S (Jerry) wrote:
>>>>> Can anyone from RedHat acknowledge that this arrangement
>>>>> would be acceptable to them? If so, that would potentially
>>>>> open the door to any public domain code.
>>>>   I don't suppose for one second that the RedHat legal team are actually
>>>> reading this newgroup. 
>>>> 
>>>>   *sip*
>>>> 
>>>>   :-)
>>> Yeeeeeaah, that was my thought :-)
>>> 
>>> To answer the question, though, that's the whole point of making a
>>> trivial change. My understanding
>> 
>>   *sip*
> 
> Was that because I answered the question, or because of the implied
> "IANAL, but..."? ;-)

  Yes!

> 
>>> is you can copyright that trivial
>>> change, which then covers the entire work, with the exception that the
>>> original PD version is still PD.
>> 
>>   Why wouldn't it just cover the trivial change then?
> 
> It does, and it doesn't, or so I understand. 

  *sip*

> Copyright law is funny that
> way. :-) Do you *really* want me to attempt an explanation, or have you
> had enough to drink already?

  No, and no!

>>> Hmm, is there a list legal<AT>redhat<DOT>com? ;-)
>> 
>>   Dunno.  You could always give it a try.  If what you get back has a
>> disclaimer more than thirty times as big as the message body, you'll know
>> you've reached a lawyer.
> 
> ...and I'll be drunk, according to the latest rule. ;-)

  Hooray!

  Well, it is Friday afternoon, after all.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2006-08-18 15:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [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
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

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='011501c6c2dd$5edfbd00$a501a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.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).