On Tue, Jul 26, 2016 at 11:12 PM, Eric Rubin-Smith <eas....@gmail.com> wrote:
> >> (A) Suggest a better name than "fossil trim" >> >> (B) Define the syntax of ARGS. >> >> (C) Define a safety mechanism that allows content to be restored if >> it is accidentally trimmed when there are no other repos available >> with which to sink. Perhaps the trimmed content gets written into a >> separate "trash-can" database? >> > > You might consider this from the converse perspective, allowing 'fossil > export' to a new fossil repo, but specifying some sort of complex boolean > selector on export. Then you at least get the safety for free since the > source repo is only read from. > fwiw, that was also my gut reaction: this sounds more like it might belong in a "filtered export" -- ----- 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
