On Wed, Mar 12, 2014 at 5:04 PM, Chad Perrin <c...@apotheon.net> wrote:
> I'm stuck in kind of a no-win situation with this, then. It's not > really appropriate to log a bug in an issue tracker without knowing it's > a bug, but nobody will tell me if it's a bug, how I should judge whether > it's a bug, or whatever else applies here. I'm not even sure yet that > what I believe to be expected behavior is expected behavior, or whether > I'm just using it wrong. > You could put in an enhancement request. What you want to do, import in to a repository with only the initial, empty commit, seems reasonable. > . . . so while I wait to see if someone will give me some guidance, it > will fall off everyone's radar, and nothing will be done, so that my > only option going forward for some of these projects will be to just use > Git. > If the only possible way to start a new repository on the server is "fossil new repoName.fossil", then a possible work around would be to do a "normal" import to Fossil, then create a "marks" file (see "fossil help export") with the RID of the initial, empty commit, then use the "--import-marks" option to the "fossil export" command to (hopefully) create something usable with "fossil import --incremental". Not sure when I will be able to experiemnt with this more.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
