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

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

From: Tobias Schäfer <tobiasschaefer_at_gmx.de>
Date: Tue, 23 Sep 2008 20:14:00 +0200

On Tuesday 23 September 2008 20:00:54 Chris Calef wrote:
> 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 copy.
> 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?

This solution also works with TortoiseSVN:



  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-23 20:14:45 CEST

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