On Mon, Aug 17, 2015 at 1:07 PM, Graeme Pietersz <gra...@pietersz.net> wrote:
> 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. > Fossil does not shun by filename, but my hash value, so you'll need to find all hashes of all versions of those files and shun those. It is likely far simpler to recreate your repo without the compromised data (and count it as a "lesson learned" for future repos). That said, i have never used shunning, and it is possible (not sure!) that shunning the first version of a file will affect (shun) following versions, as they derive from it and it's conceptually impossible to derive from something which is no longer in the repository. Perhaps someone who's better-versed in shunning can enlighten us on that. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "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
