On Tue, Mar 04, 2014 at 03:49:26PM -0500, James Turner wrote: > On Tue, Mar 04, 2014 at 03:47:31PM -0500, Richard Hipp wrote: > > On Tue, Mar 4, 2014 at 3:43 PM, Chad Perrin <c...@apotheon.net> wrote: > > > > > Trying to fork/import from Git is kinda problematic. I started by > > > creating a new project on a server: > > > > > > $ fossil init projectname.fossil > > > > > > I then cloned locally: > > > > > > $ fossil clone <u...@uri.for/projectname/index.cgi> projectname.fossil > > > > > Doesn't the git import create the fossil repo for you? Maybe you should > try doing the import into a fossil repo that doesn't already exist.
According to the "fossil help import" documentation, --incremental should work with an existing Fossil repository rather than creating a new one. > > Then you can scp that repo to your server and clone it down. This is an operation that would be much more convenient to accomplish the way I've already tried to do it, in current circumstances, and there may be a fair number of similar import/fork needs in the future, which means that it makes a lot more sense for me to figure out how to get the import into an existing repository to work -- especially because people who do not have scp access to the server at the moment may also be doing some of this work. If I just do it the way you describe, I would need to do all of this work for every instance, which is not a very reasonable state of affairs here. In any case, I would much rather (help) fix a problem, or learn how to do it right if the error is mine rather than the software's, than just sweep the problem under the rug and use a work-around. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
