On 2017-09-07 23:21, Richard Hipp wrote:
On 9/7/17, Thomas <[email protected]> wrote:
Shunning is not a way to proactively prevent files from being added to
a project. I think you probably want to use the ignore-glob. See
https://www.fossil-scm.org/fossil/help?cmd=ignore-glob for the
documentation on the ignore-glob setting. I confess that the
documentation is a bit thin at the moment and needs enhancement, but
it is what we have for now.
The idea is that you create a file in your project named
".fossil-settings/ignore-glob" and you put text in that file which is
a sequence of GLOB patterns that define files, then none of those
files will be added to the repository via the "addremove" command.
Fossil itself uses such a file, which you can see here:
https://www.fossil-scm.org/fossil/artifact/b7b945d48cfceef7
You or someone else suggested this before, and it does work for new
files. It does not work for files that have made their way into the
repository already before the ignore-glob contained these files.
Once a file made it into the repro there doesn't seem to be a way of
removing it again. I'm not talking about removing all references to the
file. It just shouldn't be distributed during the next checkout of
someone else.
What I mean is, someone who's got that file within the checkout folder
automatically causes it to be checked in again, independent of what the
ignore-glob says.
So far, I can only see one way of preventing these files from being
checked in again, and that is by shunning them. Have I overlooked or
misunderstood something?
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
