From: "Dave Korn" <dave.korn@artimi.com>
To: "'Posixtastic!'" <cygwin-talk@cygwin.com>
Subject: RE: Re: Handling special characters (\/:*?"<>|) gracefully
Date: Wed, 24 May 2006 16:34:00 -0000 [thread overview]
Message-ID: <051e01c67f4f$d3f3c4f0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <4C89134832705D4D85A6CD2EBF38AE0F3E0992@PAUMAILU03.ags.agere.com>
On 24 May 2006 15:15, Williams, Gerald S (Jerry) wrote:
> Dave Korn wrote:
>>> I actually use a version of such a library to create some of
>>> the otherwise-uncreatable files in a /dev directory (which is
>>> not on a managed mount). That way, I can do:
>>
>> Is this code public?
>
> Some of it is, sort of.
>
> I finally got permission from my company to release it into
> the public domain. I even went so far as to create a project
> on sourceforge.
> At that time, I had completed the following routines:
>
> CaseWiseCreateDirectory
> CaseWiseCreateDirectoryA
> CaseWiseCreateDirectoryW
> CaseWiseCreateDirectoryEx
> CaseWiseCreateDirectoryExA
> CaseWiseCreateDirectoryExW
> CaseWiseCreateFile
> CaseWiseCreateFileA
> CaseWiseCreateFileW
> CaseWiseSetCurrentDirectory
> CaseWiseSetCurrentDirectoryA
> CaseWiseSetCurrentDirectoryW
>
> And was working on:
>
> CaseWiseMoveFile
<lightbulb> Hey, that "CaseWise" prefix looks familiar! Yes, I came across
your old posts about it when I was looking into the use of
POSIX_FILE_SEMANTICS myself last summer. I came to fairly much the same list
of needed functions myself when I looked into the matter, and then ran out of
round tuits. I was thinking of implementing posix mount points as an
alternative to managed ones.
http://www.cygwin.com/ml/cygwin/2003-02/msg02179.html
Ah, yes, that's the thread I remember finding.
http://sourceforge.net/projects/casewise/
Heh. No files released, zero commits to cvs, one welcome post by "nobody"
in each of the forums.... it's like the Marie Celeste in there!
> Now, the whole point to the project was to make something
> available that Cygwin could use, since my company would not
> sign the release that allowing me to contribute directly.
> (This is another reason why the code couldn't be GPL'ed.)
> If you're interested, I can clean up the project and make
> sure the existing files are properly published.
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"
(albeit based on a PD work) to be submittable. IIRC, the WINE headers are
GPL'd[*], so I'll use them for any definitions I need.
cheers,
DaveK
[*] - I didn't R quite C; they are in fact LGPL'd. That is just as good for
the purposes discussed here.
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-05-24 16:34 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 [this message]
2006-05-24 16:38 ` Christopher Faylor
2006-05-24 16:52 ` Dave Korn
-- 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='051e01c67f4f$d3f3c4f0$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).