X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4AF38062.2040700@monai.ca> References: <4AF38062.2040700@monai.ca> Date: Fri, 6 Nov 2009 05:54:49 +0000 Message-ID: <416096c60911052154h79babf1av9d35a5fe25129100@mail.gmail.com> Subject: Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-63 From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 2009/11/6 Steven Monai: > Fantastic! I just upgraded from 1.7.0-62 to -63, and my daily rsync > backup script can now see that handful of files on my system with > "weird" names [containing Unicode char U+F020] that were previously > untouchable by Cygwin. > > Just wondering: What limitations, if any, are there now on the chars > from the U+F0xx range that can be used in filenames? See here: http://sourceware.org/ml/cygwin/2009-11/msg00040.html Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple