> > > (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. Eric
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
