To my knowledge subversion does not have this capability. However, I
usually will slap together a script in Ruby or Perl for these kinds of
copies, or use Beyond Compare if I'm not sure what needs to be copied.
From: Tom Malia [mailto:firstname.lastname@example.org]
Sent: Thursday, April 12, 2007 9:15 AM
Subject: Turn an unmanaged Directory into a working directory?
First, let me start with, I'm in a Windows environment.
If I've got a directory that contains some or all of the same files and
subdirectories of a repository directory in Subversion but it's not
currently a SVN working directory, what's the best way to basically turn
it into a working directory linked to the repository?
As a concrete example, let's say someone created a new repository by
importing a directory from their location machine (If memory serves,
this does not turn the source directory into a working directory
correct?) then they spend a week or so making changes to the contents of
the directory on their location hard drive (I know, that was a mistake
but this is the kind of thing that occurs). Now they want to "commit
their changes". Obviously they can't do that directly because the local
directory never got the necessary .svn folders, etc.. So, is there an
easy way to basically "Check out" the repository to that existing
directory on the local machine without over writing the current contents
of that local directory?
If any of you guru's originally worked with VSS 6X, then you may
recognize what I'm trying to do as the equivalent to: 1) Set working
folder 2) Check out w/out getting local copy...So if you use to do that
in VSS and subsequently have found an equivalent in SVN, that's what I'm
I realize that a work around would be to check out the repository to a
separate directory, then copy the files to that directory, the problem
is, in the windows environment, when you copy a subdirectory from one
directory to another, if there's already a directory with the same name
in the destination, then the copy process deletes the original directory
in the destination and replaces it with source. Subsequently the copy
solution would delete the .svn folders in the working directory if you
tried to simply copy the non-managed directory into the managed/working
directory. The only solution I see to this is a very tedious process of
manually coping the contents of each subdirectory separately, which
would be a royal pain for some the scenarios where this situation is
occurring to us.
Thanks in advance,
Received on Thu Apr 12 15:29:09 2007