Re: Workaround for 260 char limitation?
[email protected] Thu, 5 Nov 2009 10:38:14 -0500
| Newsgroups | gmane.comp.version-control.cvs.windows-nt.user |
|---|---|
| Message-ID | <OFC80DC0F4.D83CE5E5-ON85257665.00553990-85257665.0055E616@aep.com> |
[email protected] wrote on 11/05/2009 10:28:36 AM: > Hi! > Is there a workaround to avoid > http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?tt=1&id=5629 > when trying to "cvs update" a project that has path-names longer than 260 > chars? Nope. This is due to Microsoft's implementation of the NTFS filesystem (remember how we'd never need more than 640K of memory?)and is built into the filesystem (Microsoft's limit is actually 254 character from drive designator to last character of file extension). You don't mention your server/client setup as that would determine the impact to your environment. Paul Feeny > _______________________________________________ > cvsnt mailing list > [email protected] > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt > > Upgrade to CVS Suite for more features and support: http://march- > hare.com/cvsnt/ _______________________________________________ cvsnt mailing list [email protected] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/