>> I am a newcomer to Fossil, was quite surprised that hidden files are >> left out by default. > > Why? What is the definition of "hidden".
I probably should not be buying into this discussion, as I'm a newcomer. But anyway, I place files with a dot in front of them into a project because they are intended to be in the project. That's what anyone would do. So why should Fossil screen them out? A hidden file is just a file that is not normally visible. This usually pertains to the end user, when someone installs the project. I can't see any reason whatsoever why Fossil should screen them out. It does not matter whether this is Unix/Linux or not. >> Note, my Fossil repo has hidden files, symlinks, binary files, empty >> directories, and files/directories with special permissions/ownership! > > Your project has these things. To the extent that my projects have them, > I deal with them with setup, build, and install scripts. I don't actually > see why people expect a newly-made checkout (working) directory to behave > in all respects like an installed copy of the project. This is not what > the SCM tools are designed for. Er, I don't expect the SCM to behave in all respects like an installed copy of the project. Well, perhaps it would be nice if it did, but where Fossil cannot handle it, file permissions/ownership for example, I also have workarounds, in my case a post-checkout script. Regards, Barry Kauler _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
