On Mon, Apr 4, 2011 at 5:11 PM, <[email protected]> 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 > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
