Okay. I always put these in the boring file. Matter of taste I guess. <div><div><div><br><div class="gmail_quote">On Fri, Apr 3, 2009 at 3:18 PM, Ketil Malde <span dir="ltr"><<a href="mailto:ketil@malde.org">ketil@malde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Peter Verswyvelen <<a href="mailto:bugfact@gmail.com">bugfact@gmail.com</a>> writes:<br>
<br>
</div><div class="im">> Regarding these files that people forget to checkin.<br>
> Doesn't every project have a well define directory structure? Shouldn't the<br>
> "prefs/boring" file use this fact to encapsulate the rules of file inclusion<br>
> and exclusion? Isn't it safer to checkin too many files (by accident) than<br>
> forgetting one? Shouldn't this behavior be the default?<br>
<br>
</div>IMO: No. My development directories tend to litter up with files<br>
containing test input data, output data, profiling data, and all kinds<br>
of junk. Better to occasionally forget a file and get an error<br>
message in the mail when somebody else tries to use it<br>
(i.e. non-strictly) than have my darcs repository and Hackage sdists<br>
working but littered with junk. (My current testing involves 118GB of<br>
input data, you sure you want to see that on Hackage? :-)<br>
<div><div></div><div class="h5"><br>
-k<br>
--<br>
If I haven't seen further, it is by standing in the footprints of giants<br>
</div></div></blockquote></div><br></div></div></div>