On Feb 27, 2018, at 10:55 AM, Agrawal, Ritika <[email protected]> wrote: > > - Need to clean up the files manually as well
That’s consistent with the current default behavior of “fossil rm” as well, so it’s correct until/unless that changes. > - Purging happens only in local clone copy and never syncs back. > Need to copy back the clone to central repo That’s consistent with the behavior of the /shun command. I’m uncertain how these two mechanisms interact and overlap, but it is at least clear to me that they should behave the same way. I’m uncertain because I’ve never used either mechanism in all my years of Fossil use, on purpose, for philosophical reasons. The reason these commands behave that way is that, once you distribute a given artifact to someone else, you should not be able to *make* them forget that you sent it to them. It takes a collaborative effort to expunge an artifact from all repository clones, everywhere, on purpose. This is because it is necessarily a social matter rather than a technical matter: you need to convince everyone they they should also forget the artifact. This mailing list works much the same way. I cannot un-send a message to the mailing list. There is doubtless a way for drh to delete a message from the mailing list server’s archive, but that doesn’t un-distribute it to the mailing list members. I’ve occasionally regretted sending out an email to a mailing list, but I wouldn’t presume to reach into your computer to delete the copy you received to “fix” my mistake. See also: https://www.fossil-scm.org/index.html/doc/trunk/www/shunning.wiki _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
