On 9/6/17, Thomas <[email protected]> wrote: > > If I unshun > a7ffc6f8bf1ed76651c14756a061d662f580ff4de43b49fa82d80a4b80f8434a now the > next one to check in (run the check-in script) would cause all the other > empty files to be distributed to everyone else, wouldn't they? > > Why are those not removed, by the way? They got the same SHA3 key.
A file name and a file's content are distinct and separate objects. The SHUN mechanism removes file content. The file names are entries in the manifest file for a check-in and are unaffected by shunning. Shunning a zero-length file does not hide any information from anybody. Everybody can still clearly see the name of the file in the manifest, and its hash, and from the hash they can deduce that the file is empty, even if that file has been shunned. Shunning is designed to remove content from the repository, not the filename of the content. Shunning is intended, for example, to remove a file of passwords that you check-in accidently. After shunning, everybody can still see that you accidentally checked in the password file, they just cannot see the content of the password file. You seem to be wanting that the shun remove the filename too, so that nobody can see that you even checked in the file mistakenly. But that is not possible without shunning the entire check-in. -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
