On Wed, Mar 7, 2012 at 12:26 PM, Ștefan Fulea <fulea.ste...@gmail.com>wrote:
> 2012/3/7 <sky5w...@gmail.com>:
> > If you are considering cross-platform issues, is it not unreasonable
> > to add your choice of CSM's requirements?
> > A brief wiki survey lists the older win95 VFAT restrictions include:
> > |\?*<":>+[]/
> I understand the effort to prevent trouble (and that's what people
> will usually do anyway, without being forced), but the currently
> adopted solution comes itself as another problem. It doesn't make
> sense. For your example, _if_ one of the machines involved in a
> project would be potentially affected due to it's file system
> restrictions then we will address that problem by renaming our files
> accordingly to fit everyone involved in that project. Why do we have
> to rename all the files in the world? If there are tools that don't
> like some characters, then we'll settle guidelines and restrictions
> inside our development team to avoid those. Why do we have to force
> them down on everybody's throat?
> And aside from software development, Fossil on the whole has a lot of
> advantages and possess a great potential for adoption far beyond the
> programmer's world, why does it have to be hurtful with restrictions?
> Does everybody has to consider the cross-platform issues in everything
> they do?
>
The code that implements the filename restrictions is here:
http://www.fossil-scm.org/fossil/artifact/3e15b2476f1?ln=439-441
You are welcomed to comment out those lines in your own copies of Fossil if
you like.
> _______________________________________________
> 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
