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
> >
> > I imported from Git:
> >
> >     $ git fast-export --all | fossil import --git --incremental \
> >     /path/to/projectname.fossil
> >
> > I opened the repository:
> >
> >     $ mkdir projectname; cd projectname
> >     fossil open /path/to/projectname.fossil
> >
> 
> The above should be all you need to do.  It should just work.  And it does
> "just work" for every git repository that I've tried, though that is,
> admittedly, not that many repos.
> 
> If you are willing to share with us the specific repo you are trying to
> import, prehaps the developers can try it and discover what's going wrong.

    git://repo.or.cz/nvi.git

For reference, I'm using . . .

    $ fossil version
    This is fossil version 1.28 [3d49f04587] 2014-01-27 17:33:44 UTC

. . . on FreeBSD, installed from ports, with the JSON and STATIC options
both selected at build time.

-- 
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

Reply via email to