On 11 April 2017 at 14:34, Scott Robison <sc...@casaderobison.com> wrote:
> No, it is an explicit command clearly stating the user's desire for > exclusion of these files *that are not already under source control*. > The fact that the user does not remember or did not realize they > issues conflicting commands does not mean that fossil should suddenly > stop tracking the file, or so it seems to me. > > If a file was previously added to a repository (indicating a desire to > keep track of modifications to the file), that is more important than > ignoring the file. > I think --ignore should give an error if the --ignore matches a file already in the repository. The current behaviour is clearly somewhat ambiguous. Alternately (or additionally!) a command that would check and report if there is any file(s) that would match the --ignore or the ignore-glob flag would be helpful. ../Dave
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
