On Mon, Apr 10, 2017 at 2:57 PM, Thomas <tho...@dateiliste.com> wrote: > I reckon I owe you a beer! ;-)
Not at all. I don't drink, anyway. Well, not beer. :) I was surprised my first guess was off base, but actually sitting down and trying some stuff outside the large repo you're using was useful to see how things worked. > Anyway, your suggestion sounds very reasonable (ok, it doesn't sound > reasonable at all to be honest, but I think that's what happened). I think if you add a file to a repo then add an ignore, it is safer to keep maintaining it rather than suddenly ignoring it. The two events are conflicting, so fail safe. Removing the file allows it to be ignored going forward. > After reading your mail I remembered that all files that have been ignored > all along via ignore-glob or --ignore are files I deleted manually at one > point or another. > > The files that always go into the repro I've never touched but I'd added > them to the ignore list later. Glad I was able to point you in a useful direction. FYI: In looking a little at the code, I can see that there was some work related to versioned settings a couple years ago now that seems to have been put in place to check either the file in the repo or the file on the disk depending on what is available. I don't have time to understand it completely, but that seems to be the source of my confusion as to when / where versioned settings are accessed / read. -- Scott Robison _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
