On Sat, Mar 8, 2014 at 5:17 PM, Chad Perrin <c...@apotheon.net> wrote:
> > Should I take it at this point that --incremental is deprecated and > should not be used or expected to be present in future Fossil versions? > So far, I have seen no responses that specifically addressed whether the > behavior I expected from it was the intended behavior, whether anyone > else might have the same problem indicating a bug in the software or > whether this was confined to my situation and thus might be a local > configuration issue, whether there was anything I could do to provide > more information to help, and so on. The closest thing to meaningfully > addressing the issue that I have seen was akin to the old joke . . . > > patient: Doctor, doctor, it hurts when I do this! > doctor: Don't do that. > I very much doubt that --incremental would be deprecated. I suspect that no one else has tried your use case. I still haven't been able to experiment more, but it occurs to me that "fossil import --incremental" would assume that its input resulted from "git --fast-export --incremental". Further, I would expect the --incremental option to git to require that an initial non-incremental export had already been done. >From reading about Fossil export, it seems there might be a way to fake an initial non-incremental export from Fossil. If that is so (or if this can be done directly in git), then I would expect "fossil import --incremental" to work as you want. Of course, it would be useful for Fossil to support non-incremental import to an existing repository, at least one with only the initial, empty commit.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
