<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Migrating Surround SCM working directories across VMs</title> <atom:link href="http://blogs.seapine.com/2009/06/migrating-surround-scm-working-directories-across-vms/feed/" rel="self" type="application/rss+xml" /><link>http://blogs.seapine.com/2009/06/migrating-surround-scm-working-directories-across-vms/</link> <description>News &#38; views from Seapine Software</description> <lastBuildDate>Wed, 08 Feb 2012 16:53:41 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: All about the .MySCMServerInfo file &#187; The Seapine View</title><link>http://blogs.seapine.com/2009/06/migrating-surround-scm-working-directories-across-vms/comment-page-1/#comment-110</link> <dc:creator>All about the .MySCMServerInfo file &#187; The Seapine View</dc:creator> <pubDate>Thu, 02 Jul 2009 19:34:43 +0000</pubDate> <guid
isPermaLink="false">http://blogs.seapine.com/?p=486#comment-110</guid> <description>[...]  Fernando Cremer talks about Surround SCM  on July 02, 2009  Recently there have been a couple posts about moving working directories and the .MySCMServerInfo file. Some users are not sure what this [...]</description> <content:encoded><![CDATA[<p>[...]  Fernando Cremer talks about Surround SCM  on July 02, 2009  Recently there have been a couple posts about moving working directories and the .MySCMServerInfo file. Some users are not sure what this [...]</p> ]]></content:encoded> </item> <item><title>By: Jeff Schmidt</title><link>http://blogs.seapine.com/2009/06/migrating-surround-scm-working-directories-across-vms/comment-page-1/#comment-94</link> <dc:creator>Jeff Schmidt</dc:creator> <pubDate>Mon, 22 Jun 2009 14:19:30 +0000</pubDate> <guid
isPermaLink="false">http://blogs.seapine.com/?p=486#comment-94</guid> <description>Hello,
Just wanted to add a few things to this. I used to work for Seapine tech support (am now working in the Quality Assurance dept.).
This will also work if you want to move your working directory from one physical computer to another (not just VMs). I recently got a newer computer assigned to me by the IT department, as the old PC was about 5 years old, and just didn&#039;t have quite enough oomph for my current duties (it ran fine, it was just fairly slow).
I was able to just copy over my working directories from the old PC to the same locations on the new PC and just keep on working.
As for those .MySCMServerInfo files - as long as they are each in the right directory, and you haven&#039;t modified them, they should be fine. In the case where you copy an entire working directory from one drive/VM to another, each of the .MySCMServerInfo files will still be in the same directory on the new drive, so that&#039;s fine.</description> <content:encoded><![CDATA[<p>Hello,</p><p> Just wanted to add a few things to this. I used to work for Seapine tech support (am now working in the Quality Assurance dept.).</p><p> This will also work if you want to move your working directory from one physical computer to another (not just VMs). I recently got a newer computer assigned to me by the IT department, as the old PC was about 5 years old, and just didn&#8217;t have quite enough oomph for my current duties (it ran fine, it was just fairly slow).</p><p>I was able to just copy over my working directories from the old PC to the same locations on the new PC and just keep on working.</p><p>As for those .MySCMServerInfo files &#8211; as long as they are each in the right directory, and you haven&#8217;t modified them, they should be fine. In the case where you copy an entire working directory from one drive/VM to another, each of the .MySCMServerInfo files will still be in the same directory on the new drive, so that&#8217;s fine.</p> ]]></content:encoded> </item> </channel> </rss>
