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

Re: Problem: svn timing out on large directory

From: John Locke <mail_at_freelock.com>
Date: 2003-05-07 00:09:06 CEST

Yes, I can check it out elsewhere.

So is there any way to make a normal directory that already has files in
it a working directory, if some of the filenames match files in the

For example, I have some projects already in the web root on this
server, and I want to add them to the repository. I'm trying to check
out different projects out of a repository, and place the entire
directory under revision control. But after the fiasco below, I now have
in my web root, half of the files under broken revision control, and the
other half under no control.

I just want to put the web root under subversion control (ignoring a few
specific directories that are packages I can always download). What's
the easiest way to do this?

I tried deleting the .svn folders and checking out, but it doesn't let
me do that since there's already files in the directory that match
what's in the repository.

What I'd like to be able to do would be something like "svn co" in an
existing directory, and for existing files, check out the HEAD version
into the local version as the BASE, leaving the existing file in the
working version. Then running an svn status could tell me if any files
are different. Can subversion do anything like this? I'm finding myself
trying to do this a lot, in several different situations already.

Thanks for your help,


On Tue, 2003-05-06 at 14:49, Ben Collins-Sussman wrote:

> Can you do a fresh checkout? I suspect your current working copy has
> incorrect administrative data.

John Locke
Recently published: "An inexpensive e-mail server setup"
Play sports? Check in at http://teamcheckin.com
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 7 00:09:54 2003

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

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