This isn't just a problem with colon: names. Device driver names
mapped into the "DOS Device" namespace such as LPT1, COM2, etc. will
also do this to you. While you could filter on the well known ones,
there's nothing stopping an installed piece of software from making
it's device driver available in this manner with any name it wants.
The colon can get even more evil in ways you don't expect. On NTFS,
the colon means streams, although some commands try to second guess
the user and defeat them.
> C:\Documents and Settings\paulf>echo hi > file:name
>
> C:\Documents and Settings\paulf>dir file
> Volume in drive C has no label.
> Volume Serial Number is 64B4-FE20
>
> Directory of C:\Documents and Settings\paulf
>
> 02/04/2006 12:16 AM 0 file
> 1 File(s) 0 bytes
> 0 Dir(s) 127,067,172,864 bytes free
>
> C:\Documents and Settings\paulf>type file:name
> The filename, directory name, or volume label syntax is incorrect.
>
> C:\Documents and Settings\paulf>cat file:name
> hi
On Feb 3, 2006, at 7:23 PM, Andy Levy wrote:
> Bug? Not sure. You can do other things in SVN that Windows
> doesn't handle (symlinks come to mind); maybe a pre-commit hook is
> needed to check for the existence of illegal characters in file/
> directory names? If you had a non-Windows system available to you,
> you could have checked out a WC to that, removed the directory w/
> svn rm D:, committed and been in the clear
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 4 09:23:53 2006