Corinna, I **really** want to try this snapshot, but unfortunately my sys-admins have locked down access right now. There is no forecast on when I'll get access.
-Kevin > -----Original Message----- > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On > Behalf Of Corinna Vinschen > Sent: Monday, April 26, 2010 8:15 AM > To: cygwin@cygwin.com > Subject: Re: PLEASE TEST YOUR FS (was Re: 1.7.1: cvs version built in > is unstable) > > On Apr 23 13:12, Corinna Vinschen wrote: > > I didn't like this solution at all. I just applied another patch > which > > handles that differently. Instead of stripping the leading spaces > and > > trailing dots and spaces, they now get converted the same way as > > described in > > http://*cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames- > specialchars > > > > So the offending dots and spaces are converted into the UNICODE > private > > use area instead, and transparently converted back to dots and spaces > > when accessing them via Cygwin. This allows to keep the filenames > > unchanged from the user's point of view. The file > > > > " abc ... " > > > > is *still* the file > > > > " abc ... " > > > > even on the broken filesystems. > > > > Again I tested this change on NTFS with a little tweak to the code. > If > > you NetApp and NWFS users please test the next developer's snapshot > (the > > next one after 2010-04-22), I would be most grateful. > > Anybody? > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin > to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat > > -- > 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 >
