On Wed, Aug 5, 2015 at 4:52 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: > On 8/4/2015 6:06 AM, Stephan Beal wrote: >> On Tue, Aug 4, 2015 at 1:02 PM, David Mason <dma...@ryerson.ca >> <mailto:dma...@ryerson.ca>> wrote: >>> Just be careful not to shun 0 length files or you won't be able to >>> commit a 0-length file until you've cleared the shun table (because >>> all 0-length files have the same SHA-1 id. >> Excellent point, though it's hard to imagine such files being either >> binary or holding sensitive data (except maybe in their name... hmmm.... >> interesting corner case). > > Files (rather, artifacts) are not shunned by name but by contents. If a > file's name is the problem, shun the manifest containing the name. >
I suspect the answer will be "NO", but any chance I can export only a subtree of the repository (along with its history) and import into a new repositorym so to avoid having binaries? Or any chance to force sqlite to forget about such binaries? Please note: it's fine for me to keep the repo as it is, after all it was my mistake, but I would like to fix it without loosing all the history. Luca _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
