On Apr 10, 2017 5:02 PM, "Thomas" <tho...@dateiliste.com> wrote:
On 2017-04-10 22:28, Scott Robison wrote: > 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. :) > You're probably missing one of the best parts in life here ;-) 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. > I just tried it. Yepp, that was it. ;-) The --ignore argument as well as the .fossil-settings\ignore-glob file don't work for files or file masks that have been committed at some point after the repository has been created. Your work-around worked. After deleting some of these files, committing, changing, and committing again, they were ignored/not checked in afterwards. I'd say this is either a big design flaw or a bug. It's not mentioned anywhere in the documentation and is anything but logical and reasonable. Perhaps it should be documented, but I don't think it is a bug. It is the software doing the job it was originally told to do (track versions of a file) instead of doing the job it was subsequently told to do (ignore untracked files with a given glob). For example, I have licensed libraries in the past that are shipped as obj files. They need to be tracked, even though most obj files don't. This model allows you to add certain obj files which will be tracked while ignoring all others. I reckon everyone starts using software with the default settings. I'd even go a step further and say when someone starts using a source code version management software the first thing they do is give it a go and check out and in again pretty much everything they got scattered around their harddrive and every memory stick in reach. ;) The least I'd expect is that these files are not just silently uploaded but that I'd receive a message, explaining why they are uploaded. I thought I got to chuck the box out the window after I'd been asked again so many time to enter a commit note including all the files I didn't want it to include. Bear in mind, I explicitely told the software not to upload them, but it secretly ignores/drops my command. That is far from being user-friendly. ;-) Of course I'm glad to know now how to circumvent this issue. Thanks again. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
