Import then checkout

[Brian Erickson <er...@BAUERCONTROLS.com>]

I've got a soure tree with several thousand files in it.  After
importing into subversion, I'd like to make my tree a working copy.  Is
there a way to do this?  The checkout command appently expects to run on
an empty folder or a folder that is already a working copy.
 
I keep getting errors of the form: svn: Failed to add file 'filename':
object of the same name already exists.
 
It works fine if the folder is empty.
 
Brian Erickson
Bauer Controls
 

Re: Import then checkout

[Ryan Schmidt <su...@ryandesign.com>]

On Oct 26, 2006, at 12:23, Brian Erickson wrote:

> I've got a soure tree with several thousand files in it.  After
> importing into subversion, I'd like to make my tree a working  
> copy.  Is
> there a way to do this?  The checkout command appently expects to  
> run on
> an empty folder or a folder that is already a working copy.

If you use the in-place import strategy, then the directory from  
which you're importing becomes a working copy.

http://subversion.tigris.org/faq.html#in-place-import

But if you use "svn import" then no, you'll have to check it out from  
the repository to get a working copy. The ability to not have to do  
that has been requested before; looks like this one:

http://subversion.tigris.org/issues/show_bug.cgi?id=1328




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Import then checkout

[Andy Levy <an...@gmail.com>]

On 10/26/06, Brian Erickson <er...@bauercontrols.com> wrote:
>
>
> I've got a soure tree with several thousand files in it.  After importing
> into subversion, I'd like to make my tree a working copy.  Is there a way to
> do this?  The checkout command appently expects to run on an empty folder or
> a folder that is already a working copy.
>
> I keep getting errors of the form: svn: Failed to add file 'filename':
> object of the same name already exists.
>
> It works fine if the folder is empty.

Correct.  Subversion doesn't want to overwrite files/directories that
already exist that it doesn't "control."

Sounds like you wanted to do an in-place import.
http://subversion.tigris.org/faq.html#in-place-import but at this
point, you may be best off renaming (and delete once you're sure you
can get everything back out of Subversion) the current directory and
doing a checkout.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org