On 9/7/17, Thomas <[email protected]> wrote: > > There's 3 folders in the project. > a > b > c > > I can create a file a/x.ext (empty and file length of 0), which should > not go into the repository. Because if it goes into the repository > everyone else would get that file. The pure existence of that file > changes the behaviour of some script. This behaviour is the personal > preference of the contributor. > > In other words, everyone should be able to create a a/x.ext or a b/x.ext > or a c/x.ext without having these files uploaded/checked in/shared > between repositories. > > Shunning means no one can upload these files because their SHA3 hash is > shunned. Am I correct here or did I misunderstand something?
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 -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
