I generate the initial fossil for them. The problem is that I don't control, e.g. executable names, so if they have foo.c and say `make foo` they will have foo.o which I can match, but also foo which I can't (because they might call it foox.c - and hence foox - instead).
Because I generate the initial fossil the `:::BINARY:::` pattern in the ignore-glob file is viable, as would be a `:::SizeOver:::100000` pattern. I'm mostly not worried about them intentionally or maliciously creating cruft, but rather accidentally and carelessly. ../Dave On 10 May 2017 at 09:50, Andy Bradford <amb-fos...@bradfords.org> wrote: > Thus said David Mason on Wed, 10 May 2017 01:07:22 -0400: > > > 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! > > Do students generate their own Fossil, or is the Fossil generated for > them? If it is generated for them, why not just commit an ignore-glob > that covers the kinds of large files they are likely to generate to the > .fossil-settings directory? > > Andy > -- > TAI64 timestamp: 4000000059131ac8 > > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
