Re: [fossil-users] Fossil cannot add filenames with \*[]?
On Mon, 4 Apr 2011 19:37:07 -0400 Ron Wilson ronw.m...@gmail.com wrote: Fossil failed on filenames containing brackets - []. Huh? Browsing the mail shows this to be a known issue. Browsing the responses came up short. Any glaring reason(s) for not allowing certain wildcards in filenames? Especially when competing SCM's are already past this... In some development environments, these characters are not a problem. Only the characters used by the file system, such as / in Unix/Linux and \ and : in Windows, are not allowed in file names. However, in environments that, directly or indirectly, use command line processing, such as shell scripts, .BAT scripts and even make files, these characters are often used for other purposes and will cause problems if not properly quoted and/or escaped. That typically adds ', and \ to the list of problem characters. Also, ; is often used as a command delimiter, and the space and tab characters are often used as parameter delimiters. [...] All that said, however, it would make sense to make the prohibition of these characters a configurable setting. There are plenty of new developpers who have never had to worry about these restrictions, so will likely choose an SCM that either lacks these restrictions or can be configured to disable them. I concur. There is a huge difference between having the need to tweak something to get the desired functionality and complete inability to get it (commenting out some source code would be a solution only in a tiny fraction of possible cases, I reckon). So, a user-configurable setting to switch off banning of this additional set of characters in filenames would be just OK I think. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil cannot add filenames with \*[]?
Hi, This weekend I was shouting praises of Fossil to a friend in the release business and he summarily shot me down with a simple attempt to add his Subversion based repository. Fossil failed on filenames containing brackets - []. Huh? Browsing the mail shows this to be a known issue. Browsing the responses came up short. Any glaring reason(s) for not allowing certain wildcards in filenames? Especially when competing SCM's are already past this... I don't use these characters myself, and continue to use Fossil. -Steve ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil cannot add filenames with \*[]?
On Mon, Apr 4, 2011 at 5:11 PM, sky5w...@gmail.com wrote: Hi, This weekend I was shouting praises of Fossil to a friend in the release business and he summarily shot me down with a simple attempt to add his Subversion based repository. Fossil failed on filenames containing brackets - []. Huh? Browsing the mail shows this to be a known issue. Browsing the responses came up short. Any glaring reason(s) for not allowing certain wildcards in filenames? The reason such names are disallowed is because they are prone to error. Not in Fossil itself, but in other software. For example: optional external merge and diff programs that people might choose to set up. So for safety's sake , Fossil goes to the extra trouble of disallowing them. Note that it is extra code that checks for these filenames and disallows them. This is not a bug. It is a feature I deliberately introduced and which I am loath to take out. But if you really want to disable it, it is simply a matter of commenting out some code. Especially when competing SCM's are already past this... I don't use these characters myself, and continue to use Fossil. -Steve ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil cannot add filenames with \*[]?
Hi, I looked at the offending files and the brackets as you may have guessed contained incremental numerals. something[1].bin, something[2].bin, etc. Given the filenames are accepted by the O/S, wouldn't it be more prudent to optionally allow these and other wildcards? I'm no fan of branching off for want of a file filter. ;) -Steve On Mon, Apr 4, 2011 at 5:23 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Apr 4, 2011 at 5:11 PM, sky5w...@gmail.com wrote: Hi, This weekend I was shouting praises of Fossil to a friend in the release business and he summarily shot me down with a simple attempt to add his Subversion based repository. Fossil failed on filenames containing brackets - []. Huh? Browsing the mail shows this to be a known issue. Browsing the responses came up short. Any glaring reason(s) for not allowing certain wildcards in filenames? The reason such names are disallowed is because they are prone to error. Not in Fossil itself, but in other software. For example: optional external merge and diff programs that people might choose to set up. So for safety's sake , Fossil goes to the extra trouble of disallowing them. Note that it is extra code that checks for these filenames and disallows them. This is not a bug. It is a feature I deliberately introduced and which I am loath to take out. But if you really want to disable it, it is simply a matter of commenting out some code. Especially when competing SCM's are already past this... I don't use these characters myself, and continue to use Fossil. -Steve ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil cannot add filenames with \*[]?
On Mon, Apr 4, 2011 at 5:11 PM, sky5w...@gmail.com wrote: Fossil failed on filenames containing brackets - []. Huh? Browsing the mail shows this to be a known issue. Browsing the responses came up short. Any glaring reason(s) for not allowing certain wildcards in filenames? Especially when competing SCM's are already past this... In some development environments, these characters are not a problem. Only the characters used by the file system, such as / in Unix/Linux and \ and : in Windows, are not allowed in file names. However, in environments that, directly or indirectly, use command line processing, such as shell scripts, .BAT scripts and even make files, these characters are often used for other purposes and will cause problems if not properly quoted and/or escaped. That typically adds ', and \ to the list of problem characters. Also, ; is often used as a command delimiter, and the space and tab characters are often used as parameter delimiters. As antiquated as it may sound, there as still many tools that assume these restrictions are in place. (As an FYI. even Windows admins use a command line environment, especially for custom automated procedures, which is why Windows still has a command line.) All that said, however, it would make sense to make the prohibition of these characters a configurable setting. There are plenty of new developpers who have never had to worry about these restrictions, so will likely choose an SCM that either lacks these restrictions or can be configured to disable them. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil cannot add filenames with \*[]?
Hi, I noticed fossil will not add files containing any of the characters \*[]?. If I remove the checks for these chars, I cannot find any adverse effects. Is there a specific reason these characters are forbidden? Regards, Mark ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil cannot add filenames with \*[]?
On Mon, Aug 17, 2009 at 12:06 PM, Mark Janssen mpc.jans...@gmail.comwrote: I noticed fossil will not add files containing any of the characters \*[]?. If I remove the checks for these chars, I cannot find any adverse effects. Is there a specific reason these characters are forbidden? The ?:* characters are forbidden by FAT/VFAT filesystems. i cannot account for the [] being forbidden - it may be limited on other platforms (i just tried it on WinXP and Solaris 10, and [] are allowed there). -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil cannot add filenames with \*[]?
On Mon, Aug 17, 2009 at 3:08 PM, Stephan Bealsgb...@googlemail.com wrote: On Mon, Aug 17, 2009 at 12:06 PM, Mark Janssen mpc.jans...@gmail.com wrote: I noticed fossil will not add files containing any of the characters \*[]?. If I remove the checks for these chars, I cannot find any adverse effects. Is there a specific reason these characters are forbidden? The ?:* characters are forbidden by FAT/VFAT filesystems. i cannot account for the [] being forbidden - it may be limited on other platforms (i just tried it on WinXP and Solaris 10, and [] are allowed there). -- - stephan beal http://wanderinghorse.net/home/stephan/ Hmmm for [] VMS comes to mind. So fossil takes the common denominator for file names on all platforms? Although that's certainly good for portability of the repos, it does limit the artifact names you can use. Renaming the artifacts to a name which is allowed, is not always an option. Perhaps a warning would be more appropriate? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
