On Thu, Sep 23, 2010 at 3:20 PM, Richard Hipp <[email protected]> wrote: > The "deconstruct" method is fossil's equivalent to fast-export. Why does > this not meet your needs and what exactly are you looking for? Are you > wanting an export in the git-specific format? How could we export wiki and > tickets in that case?
This may be a PEBKAC issue, but when I run deconstruct, I end up with an unordered tree of hashes. I'm not sure how I would parse any linear history out of that, even on a per-file (rather than a per-project) basis. Since I don't really understand how the wiki and tickets are stored inside fossil, I don't know why that's a special case. It may very well be, but I can't address that intelligently. For example, on GitHub my wiki is just a git repository of text files, so the wiki is versioned identically to any other object. Ticgit does something similar with in-repository trouble tickets; they're just versioned text files in a special git branch. I'm uncomfortable with data silos. I'm freely admitting my ignorance of fossil internals; I'm just basically asking how locked in I am if I start a project in fossil and then ever need to migrate out of it. There's usually a loss of metadata associated with any import/export, but I'm just trying to understand what the options are and how much history I could take with me. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
