On Thu, May 31, 2018 at 8:03 PM, Миндров Евгений <eugene.mind...@yandex.ru> wrote:
> Well, now I'm in a situation which has been discussed here many times - I > need to "unmake" certain file attachment from a repo, make it look like it > had never been there. > > I know it goes against the core values of Fossil philosophy and it's akin > to replacing all fossilized trilobite remains in Paleozoic strata with > Oreos so paleontologists would scratch their heads, but anyway. > It's not just against the values, it's against the implementation! There is only one way to nuke data in fossil, and it should only be used as a last-resort option, not in day-to-day maintenance. (i've been using fossil since Christmas of 2007 and have never once used this feature.) fossil help purge provides these warnings: ==== WARNING: This command can potentially destroy historical data and ==== ==== leave your repository in a goofy state. Know what you are doing! ==== ==== Make a backup of your repository before using this command! ==== ==== FURTHER WARNING: This command is a work-in-progress and may yet ==== ==== contain bugs. i.e. don't use that feature ever unless you know for a fact that you absolutely need to. Instead, you "want" (but don't REALLY want) the shun feature. It's only accessible in the UI under the Admin pages (the URI is /shun). You enter the UIDs of the artifacts to shun and it will permanently remove them from your repo. Be sure to read the documentation on that page. PS: you _really_ don't want to remove data from your repo unless someone checked in a password, private SSH key, something copyrighted by someone else, or similar cases. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users