On May 10, 2017, at 7:59 AM, David Mason <dma...@ryerson.ca> wrote: > > Actually a flag that caused `fossil add` and `fossil addremove` to treat > binary files as if they were in the ignore-glob would be perfect
How about a reject-glob setting? In your case, you could provide this file, knowing the file types your students will be working with. This new setting would behave much like ignore-glob, except that it would only affect fossil add and addremove, and unlike ignore-glob, explicit mention of the rejected matching file names in an “add” command would not override the setting. I don’t like the idea of a setting that would reject binary files. There are just too many cases where that *is* what you want. (e.g. PNGs in a web-based project.) > It would also be convenient if these were exported configuration so when they > first clone the repo their local repo gets the configuration. This proposed reject-glob setting would be versionable. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
