I work at a company that is currently using SVN + Bugzilla for SCM.  It's 
painful, and I am experimenting with Fossil on one of my local VMs to trial a 
parallel process for tracking all the changes.  Fossil's out of the box UI is 
fantastic and just what we need.

My goal is to set up a separate Fossil environment that gets refreshed from SVN 
on demand.  Since I know of no direct SVN -> Fossil integration, I need to go 
through git (which is fine).

To achieve this goal, I use `git svn` to do the initial import and fetch 
changes.  Then, I use `git fast-export`, passing a `gitmarks` file with all the 
changes that have already been exported.  Script below.

This all works fine, with one significant exception.  When I do a diff 
operation on many files that are updated during the incremental import, it 
appears that the entire file is "new."  In other words, the left hand side of 
the diff is blank and the right hand side is entirely green.  If I do a unified 
diff, the entire screen is green.  I look at the patch, and it's filed with 
plus signs.  Etc.

My fossil version is from June 14, I fetched the tip of the repository and 
compiled.

I did look at the output of `git fast-export` but am not well versed enough in 
the format to be able to identify problems.  I'm aware that the problem could 
very well lie outside of fossil, but figured I would start with this user group.

Any ideas?  Thank you in advance.




#!/bin/bash

PWD=$PWD
cp gitmarks gitmarks.bak
cd git
git svn fetch
git fast-export --all \
                --import-marks=../gitmarks \
                --export-marks=../gitmarks \
    | fossil import --git --incremental ../forerun.fossil
cd ..
_______________________________________________
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