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

faster new-project-to-working-copy method?

From: Chris Calef <chris.calef_at_gmail.com>
Date: Tue, 23 Sep 2008 11:00:54 -0700

Hi svn users list,

Apologies if this has been asked a million times, I couldn't find it in the
archives... anyway, I've been using Tortoise SVN for years, and the one
thing that has always frustrated the heck out of me is the fact that there
is apparently no way around having to import a project to a repository
(upload) and then check it out again (download) to get a usable working

I know that's standard SVN protocol, or at least the way I've always done
it, but with large projects, even on a decent connection, uploading all that
data and then having to sit and wait to _download_ all the same files again
just to get the svn info overlaid on it seems painfully inefficient. If I
was TortoiseSVN and I was writing such a fancy, easy, all-around incredibly
useful SVN client, I would think I would have addressed this issue by making
a special checkout-to-existing-copy function that checked for the existence
of files before downloading them, and only copied the .svn directories down.

So what's up, svn users, has that been there the whole time and I just
neglected to RTFM? Or is there some critical SVN reason why it wouldn't
work? Or is it on the list to go in the next version?

Chris Calef
Eugene, OR
Received on 2008-09-23 20:01:08 CEST

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