I have a Fossil repo that I expected to only work on myself. I have files containing confidential information and I now need to allow someone else developer access (so clone, push and pull as a minimum) to the repo.
I need to do two things: 1) remove past versions of one file that used to contain confidential information (it was removed in the latest commit). Does that mean shun, rebuild and then add again? How do I ensure all past versions are removed? This file has also been renamed so I need to check versions using the old path are sunned as well. 2) ensure that I have never committed another file, and, if I have, shun it completely. 3) shun two files that have been removed, but old versions of which are in the repo. They are not hard to find in the UI. All the files concerned have a distinctive filename pattern (all start the same) and would only ever have been in one of two directories in any version. Not sure if that helps. I would be very grateful for any help. Graeme -- Graeme Pietersz http://moneyterms.co.uk/ http://pietersz.net/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
