Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 2

Having Svn and Git Share The Same Sandbox?

Solved! Go to Solution.

I'm migrating from Svn to Git, and during the migration process, I'd like to have Svn and Git share a sandbox.  What I mean is that my sandbox would have both a .svn and .git folder.  My workflow would be to make code changes, commit to Svn, then commit to Git.

 

Question #1:  Has anyone done this?  Will it work?  Can the two products share a sandbox?

 

The reason the migration will take a bit of time is that I use Svn keyword substitution to embed strings that are used by the software to figure out what version it is.  There doesn't seem to be the equivalent of keyword substitution in Git.

 

Question #2:  Are there any example smudge and clean scripts anywhere on Github?

 

Thanks!

1 Reply
Solution
Copilot Lvl 3
Message 2 of 2

Re: Having Svn and Git Share The Same Sandbox?


@dtashley wrote:

I'm migrating from Svn to Git, and during the migration process, I'd like to have Svn and Git share a sandbox.  What I mean is that my sandbox would have both a .svn and .git folder.  My workflow would be to make code changes, commit to Svn, then commit to Git.

 

Question #1:  Has anyone done this?  Will it work?  Can the two products share a sandbox?

 

 


 

Here it could be a challenge to keep the ignored files/directories in sync for both systems (except for each other's .svn and .git directories) so you do not add anything unintentionally, and preventing the two remote repositories from diverging. In my experience the git-svn mechanism is very handy to assist in such a migration, including pushing any outstanding changes to both remotes and converting ignore lists.