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

RE: Re: another question: not a working copy

From: Gale, David <David.Gale_at_Hypertherm.com>
Date: 2006-08-14 19:52:22 CEST

developer@wexwarez.com wrote:
>> 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
> 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.

Well, no, you checkout the initial (empty directory), which is a very
fast operation regardless of network, since revision 0 is empty. You
then svn add your files, which doesn't hit the network at all, and then
commit the add, which sends the same amount of information as the import
would have. Unless, of course, you take advantage of the multi-step
nature of the process by setting properties or ignoring files. There's
only one add.

I'm a big fan of in-place imports, and have never actually done one the
hard way. Using the svn import command, followed by deleting &
replacing the working copy, requires two full trips to the repository,
and if you're not careful, you can end up with the imported data in a
different directory than you intended.

Just my two zorkmids, really.


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:53:49 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.