On Tue, Mar 04, 2014 at 04:01:36PM -0500, Richard Hipp wrote: > I did this: > > mkdir nvi > cd nvi > git clone git://repo.or.cz/nvi.git > cd nvi > git fast-export --all | fossil import ../nvi.fossil > cd .. > mkdir n2 > cd n2 > fossil open ../nvi.fossil > > The result was a directory full of files. And I could do "fossil ui" to > see the complete development timeline, and so forth.
My understanding is that "--incremental", as used in my original attempt described in my email to start this thread, should allow me to import into an existing Fossil repository. That is where I am having a problem. Do I misunderstand the intended use of "--incremental"? Is there some way to let someone push from a fresh Fossil repository created by import from git to an existing repository on another server, which I could use instead? The key here is that someone without the ability to brute-force copy (i.e. scp) the projectname.fossil file to the server should be able to import from git then use the fossil utility to push that to a repository on the server, resulting in a repository full of files and history. Is that possible, or do I pretty much need to either throw away all history or just stick with Git instead? -- 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
