http://xentek.net/articles/513/one-working-copy-to-rule-them-all-git-svn/?utm_source=rss&utm_medium=rss&utm_campaign=one-working-copy-to-rule-them-all-git-svn Mon, 30 Jan 2012 14:02:09 +0000 hourly 1 http://wordpress.org/?v=3.4-alpha-19827 http://xentek.net/articles/513/one-working-copy-to-rule-them-all-git-svn/#comment-1575 Roundtripping Versions: How to Git to SVN (and Back Again) Wed, 10 Feb 2010 22:00:30 +0000 http:/xentek.net/?p=513#comment-1575 [...] The basic idea is to create a new local Git repository by importing the contents of the remote Subversion repository and then move Git’s tracking data to an existing SVN working copy on your computer: “one working copy to rule them all.” [...] [...] The basic idea is to create a new local Git repository by importing the contents of the remote Subversion repository and then move Git’s tracking data to an existing SVN working copy on your computer: “one working copy to rule them all.” [...]

]]> http://xentek.net/articles/513/one-working-copy-to-rule-them-all-git-svn/#comment-1574 Eric Marden Tue, 29 Sep 2009 21:00:19 +0000 http:/xentek.net/?p=513#comment-1574 By default the git clone wanted to take the same folder name as my existing working copy. I could have specified another name for it too, but sometimes I'm overly specific in my steps to keep all the moving parts straight in my head. By default the git clone wanted to take the same folder name as my existing working copy. I could have specified another name for it too, but sometimes I’m overly specific in my steps to keep all the moving parts straight in my head.

]]> http://xentek.net/articles/513/one-working-copy-to-rule-them-all-git-svn/#comment-1573 Justin Blake Tue, 29 Sep 2009 20:46:16 +0000 http:/xentek.net/?p=513#comment-1573 Very clever idea. But why did you need to move your workingcopy folder first? Very clever idea. But why did you need to move your workingcopy folder first?

]]>