Leo, I think that you have described fairly well the situation.
I am a Unix/Windows user since the Silicon Graphics time. I would never put brackets on a file name. However, I fail to understand why the SCM tool should prohibit to do so to people that think differently. Specially on Windows, where people use the command line utilities less often. Maybe add a warning when doing "fossil add", and explain that they will not be able to put a link to that file in the Wiki, and that's it. To create a fossil branch with the modification is a practical idea only if you are a lonely developer or in a very controlled team. How do you say to a new developer?: Please use fossil, but not the standard one, because it has a strange limitation in character names for files. RR 2012/3/9 Leo Razoumov <slonik...@gmail.com> > On Fri, Mar 9, 2012 at 04:18, Gour <g...@atmarama.net> wrote: > > > > What do you mean 'pre-existing'? Software is created by you. Can you > > show me some sotware project using names with such funky characters? > > > > Gour, > one size fits all does not work in real life. For instance, brackets, > spaces, etc. are used in file names generated by certain medical > imagining machines. And when you deal with medical technicians, > nurses, medical students and above all physicians telling them that > your software cannot handle file names with spaces is a sure bet to > loose their interest. I agree that if I am naming a file, I will > produce a name that is shell friendly and avoid using random > characters. But I should be able, in principle, to import someone > else's file which is named using different conventions. That said, I > personally have no problem maintaining a separate branch where I > modify fossil code to suit my needs. > > >> We've already seen that someone who wants to store OOXML files in a > >> 'diff'-able way, will have to jump through extra hoops to get the > >> "[Content-Types].xml" file into fossil. > > > > OOXML files are 'binaries', not diff-able and therefore not suitable for > > 'software configuration management'. > > > > You can think of OOXML as compressed tar archives. They are text XML > files underneath. You can diff and merge them the same way you diff > and merge regular XML or HTML files. You just store and track OOXML > files in expanded form. > > > > > First of all educate people how to name files and/or then write simple > > script to batch rename those files before checking them into fossil. > > > > Tooling and retooling should not be too intrusive. Remember, tools are > here to help people not to add extra hustle to their already complex > work. If your tool is a nuisance people will shun using it. Not > everyone is as passionate about SCM tools as people on this list. > > > is such a problem for you to adopt a Fossil, then I might say that you > > do not have enough experience with (D)VCS in general to be able to > > appreciate everything which Fossil does so superbly. > > Otoh, you can try Git/Mercurial/Bazaar/Monotone if you believe that this > > feature is critical for you & your team. > > Please, keep discussion devoid of emotions. It is a technical list and > we are all friends here. > > --Leo-- > _______________________________________________ > 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
