On Thu, May 7, 2015 at 5:39 AM, Alaric Snell-Pym <ala...@snell-pym.org.uk> wrote:
> > For various reasons, I'd like to split the wiki out of a repo I have > into a fresh new repo of its own. I'm guessing I can do something like a > fossil deconstruct, delete anything that's not a wiki-change artifact, > and then reconstruct the result. > > 1) Would that work? > I think it would work. I do suggest you make sure to not delete the initial, empty commit (a manifest with no F or P cards) > 2) How do I reliably tell what's a wiki-change artifact? The > fileformat.wiki page suggests that any artifact that looks like a wiki > page artifact is one, but I'm not clear on how this stops files in that > form committed to a repo from then popping up as wiki pages... > You are right, a file that looks like a valid wiki (or other) artifact will be treated as an artifact of that type. While one might argue this is a flaw, I will point out that it is possible to create "fake" artifacts for other VCSs. While enhancing Fossil to check for and warn about files that look like control artifacts during a check-in could reduce the risk of accidentally introducing fake artifacts, it won't prevent some one who is determined to inject fake artifacts from doing so.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
