[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: another question: not a working copy

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-14 19:45:06 CEST

On Aug 14, 2006, at 19:30, developer@wexwarez.com wrote:

>>> So i did a remote import into my mbsrepos repository:
>>> svn import repostest http://xx.xx.xx.xx/svn/mbsrepos/repostest -m
>>> "test
>>> initial import"
>>> This worked fine. But then i decided to add a file:
>>> $ svn add repostest/trunk/file3.java
>>> svn: 'repostest/trunk' is not a working copy
>>> So when you perform an import it doesn't actually create all
>>> the .svn
>>> files that connect your files with the repository. How do you
>>> get that
>>> connection?
>> Import only takes the directory you point it at and loads it into the
>> repository.
>> If you want to keep that directory around *and* make it a WC, I think
>> you're looking for an in-place import.
>> http://subversion.tigris.org/faq.html#in-place-import
>> Since you've already done the import, you can either delete or move
>> the imported copy to another location, then check out from the
>> repository to the place where you need it.
> Ahh so you just add the root of your project directory and then do
> an add
> on the rest and commit. Kind of a pain there should be an import-
> update
> command or something that imports the data and makes the repository
> usable. I guess it doesn't matter if you are local but working
> remotely
> with large files i think this would be nice.

It's an open feature request (since 3 years ago):


In the mean time, your options are to import a directory, then
discard the directory and check it out again from the repository, or
do the in-place import that Andy suggested.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 14 19:47:29 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.