>Number: 171347 >Category: misc >Synopsis: Filename conflict in subversion >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Sep 05 15:30:01 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Jerker Bäck >Release: current >Organization: >Environment: Interix max 6.1 10.0.7063.0 genuineintel Intel64_Family_6_Model_26_Stepping_4 >Description: It's not an unlikely event or wish to checkout FreeBSD source on a Windows machine. There are however some potential risks of filename conflicts in the Windows NTFS filesystem. Here is a list of forbidden names: http://blog.onetechnical.com/2006/11/16/forbidden-file-and-folder-names-on-windows/
As it happens, FreeBSD source contains files with forbidden names in Windows, making it hard to checkout the source. share/examples/libusb20/aux.* Some tools may bypass the rules and succeed even if the names are illegal (e.g. Cygwin subversion), which is actually worse than fail. Would it be possible for FreeBSD to rename these files to something nicer for us poor Windows users? :) >How-To-Repeat: Checkout FreeBSD (svn://svn.freebsd.org/base/head) by Collabnet subversion tools for Windows (http://www.collab.net/products/subversion). >Fix: rename share/examples/libusb20/aux.c share/examples/libusb20/aux.h to something else >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
