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

Re: Re[2]: 'Import' a Working Copy?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-06-08 04:04:40 CEST

On 6/7/06, Fernando P. Nájera Cano <tortoisesvn@fernandonajera.com> wrote:
> Hi,
>
> > Perhaps though if I R> kept the .svn directories and deleted
> > everything else.
>
> I once needed to do something similar: to manually import different
> "tags" of the same project from SourceUnSafe, with files added/deleted
> between those tags. No existing tool was useful for me, so I went to
> the hard way - fortunately there were a handful relevant revisions
> only.
>
> After commiting, drop everything but .svn folders - maybe a shell
> script can help here -, place the new files on WC and go to "Check for
> modifications" (remember to tick "show all files"): any file which is
> "missing" should be deleted; any file which is "normal" should be
> added (you can do both from that dialog, and sorting on status does
> really help). Then commit. The only problem is deleted folders: using
> this method you'll keep the empty folders.
>
> Dirty but it does the trick quite well.

I do almost this same thing. For the application I manage, I need to
keep track of changes to the database schema and do so by keeping the
scripts that can be used to generate the tables in the repository. On
a monthly basis, we have generate new copies of the scripts for all
the DB objects. I delete all the files from my WC, then place the new
ones in their place. I check the status of the WC, remove any missing
files from the repository (svn del), add any new ones, and then
commit.

I'm lucky here in that everything is in one directory. It's a kludge,
but it works.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Jun 8 04:04:47 2006

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

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