From: "Dave Korn" <dave.korn@artimi.com>
To: "'not the licensing list!'" <cygwin-talk@cygwin.com>
Subject: RE: Re: Handling special characters (\/:*?"<>|) gracefully
Date: Wed, 24 May 2006 16:52:00 -0000 [thread overview]
Message-ID: <052201c67f52$66577010$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060524163854.GC25356@trixie.casa.cgf.cx>
On 24 May 2006 17:39, Christopher Faylor wrote:
> On Wed, May 24, 2006 at 05:33:46PM +0100, Dave Korn wrote:
>> Look, since your company is happy with the code being PD, then maybe
>> you should just slip me a copy in email, and I will re-work it (using
>> your PD code as a specimen/example) into a form that would be
>> sufficiently "my own work"
>
> Somehow I don't think intellectual property law works that way.
>
> cgf
Hey, maybe I have read too much into the term "PD", but I don't see how the
same sort of accusations of contamination by proprietary code could arise.
However if there's that much of a problem, never mind it. I'll just have to
take the list of function names from the post and start from scratch.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-05-24 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 16:05 Williams, Gerald S (Jerry)
2006-05-24 16:34 ` Dave Korn
2006-05-24 16:38 ` Christopher Faylor
2006-05-24 16:52 ` Dave Korn [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 14:04 Williams, Gerald S (Jerry)
2006-05-25 13:45 Williams, Gerald S (Jerry)
2006-05-25 13:55 ` Dave Korn
2006-05-25 14:35 ` Christopher Faylor
2006-05-26 5:21 ` Joe Smith
2006-05-26 5:40 ` Christopher Faylor
[not found] <4C89134832705D4D85A6CD2EBF38AE0F3E0956@PAUMAILU03.ags.agere.com>
2006-05-24 9:31 ` Dave Korn
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='052201c67f52$66577010$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).