I've described before how I use fossil to manage student assignment submissions in courses I teach.
A perennial problem is that the students commit binary executables, .o files, and the like. Theses change every build so I have dozens of versions of potentially large files in the student repos. Disk is cheap, but when you have hundreds of students committing multiple versions of multi-megabyte, it adds up. If the students were very disciplined, they would assiduously edit ignore-glob to prevent this. But if there is one thing that students (en-mass) are not, it's disciplined! So I need something on the server side that will block large and/or binary files from being saved (like an implicit shun). Any ideas? Thanks ../Dave
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users