On Tue, Aug 4, 2015 at 5:23 PM, Ron W <[email protected]> wrote: > I think this would be a useful feature. >
To me this all sounds like fossil enforcing project-specific policy, which is something it most certainly should not be doing. Case in point: [odroid@host:~/fossil/cwal/s2]$ ls -d * 1 mod_porex.c s2_protos.o 1.b mod_porex.o s2sh 1.csv mod_porex.s2 s2sh.history 1.e mod_porex.so s2sh.s2 <huge snip> mod_popen.o s2_pf.c Z.s2 mod_popen.s2 s2_pf.o mod_popen.so s2_protos.c [odroid@host:~/fossil/cwal/s2]$ ls -1 | wc -l 166 [odroid@host:~/fossil/cwal/s2]$ ls -1 *.c *.h Makefile *.sh *.?pp | wc -l 46 roughly 1/4th of those files are in source control, and it would absolutely kill me for fossil to say, "hey, buddy, you've got 120 files I don't know about! Do something about that before continuing!" To which my response would most certainly be a chain of expletives. Maintaining an ever-growing ignore-glob for an arbitrary number of globs, just to enforce a policy invoked in _someone else's project_ would be a highly unattractive option. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
