title: Can perforce create another workspace with a clone of an existing workspace that is maintained separately?
body: <p>I have an interesting question in which someone has developed some code using perforce as a repository and have made several changes to the source code that has not been checked in.  Rather than check the code in over the original however, they want to create a separate "workspace" that is a clone of the current workspace with the files still synced, but newly created files.</p>
  
  <p>I know this is not exactly how perforce should be used, but it is just a question I have to see if it's even possible or if there are better ways to to mitigate this situation in the future.  It seems like it should be possible because that's why you have separate clients each with their own "local" copies.  What not two "local" copies on the same machine?</p>