On Saturday 04 February 2006 03:23, Paul Forgey wrote:
> 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.
A simple solution is to filter such things in a pre-commit hook; here's an
example using unix shell syntax:
if svnlook changed -t "$TXN" "$REPO" | grep ^A | grep ':'; then
echo Files or directories with colons in their name are not permitted >&2
echo due to windows interoperability concerns. >&2
I don't know windows scripting syntax, but this should be easy enough to port
to whatever scripting languages you have available.
Received on Mon Feb 6 23:58:02 2006
- application/pgp-signature attachment: stored