Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 11 Jun 2003 17:51:50 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ':' - was rsync.. Message-ID: <20030611215150.GB28012@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <07e001c3305e$f76200c0$0f00a8c0 AT p4xp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <07e001c3305e$f76200c0$0f00a8c0@p4xp> User-Agent: Mutt/1.4.1i On Thu, Jun 12, 2003 at 07:18:12AM +1000, Robert Collins wrote: >Sorry for not replying in thread - I deleted the email a little fast >:p. > >Anyway, ':' is -not- in the POSIX portable filename character set: >http://www.opengroup.org/onlinepubs/007908799/xbd/glossary.html#tag_004_000_ >207 > >':' as a special behaviour is not a Windows invention, it harks (in >windows' case) from the VMS roots, and perhaps further back still. > >Secondly, solutions to handle ':' -will- involve not writing the ':' to >disk, which means parsing and interpreting the filename for validity on >every open, and during opendir etc. It's overhead - do we need it... I'm working on a per-mount option that would allow UNIX-like flexibility in filename choice. It's something tha Red Hat thinks it vaguely needs so I thought I'd do it in my spare time when I'm not being driven crazy by management issues and politics. For the record, I am nowhere near a working implementation right now and I don't have any ETA. cgf -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/