On 2017-09-07 22:49, Richard Hipp wrote:
On 9/7/17, Thomas <[email protected]> wrote:
The SHA3 hash for an empty file is in the shun list. What is going to
happen if I remove this entry? Would all those "suppress warning" files
be distributed among the team, i.e. would I with my next checkin turn
off all warning messages for everyone else?
I do not understand from your description what it is you are trying to
accomplish.
Nevertheless, I know that an empty file should not be on the shun
list. I have a note to enhance Fossil to make adding an empty file to
the shun list an error.
At the very least, you should remove the empty file hashes from your
shun list. That may or may not fix your problem. I cannot say
whether or not doing so will fix your problem because I still do not
understand your problem.
I am also concerned that you might be trying to use shunning for a
purpose different from what it was intended. But since I don't
understand what you are trying to do, I am unclear on that point too.
I was afraid of that ;-)
The project contains a file x.ext. It's content is empty and its file
length is 0.
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.
The reason for this is because someone might prefer a a/x.ext and a
c/x.ext but no b/x.ext file.
Shunning means no one can upload these files because their SHA3 hash is
shunned. Am I correct here or did I misunderstand something?
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
