On 5/14/2016 4:59 PM, John P. Rouillard wrote: > fossil init shun.fossil > mkdir shun > cd shun > fossil open ../shun.fossil > echo 2 > 2 > fossil addremove > fossil ci -m "initial commit" > echo 2a > 2 > fossil ci -m "second commit" > echo 2b > 2 > fossil ci -m "third commit" > echo 2shun > 2 > fossil ci -m "fourth shunable commit" > echo 2c > 2 > fossil ci -m "fifth commit" > echo 2d > 2 > fossil ci -m "sixth commit" > > then shun the forth commit. You can rebuild the repo if you like it > makes no difference.
Go look in /bloblist and you'll find that 2shun is still there, even after a rebuild. You've not actually succeeded in removing the dangerous data from your repository. It's still there despite not being connected to anything. -- Andy Goth | <andrew.m.goth/at/gmail/dot/com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
