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

Can't commit after switching working copy

From: Erik Hensema <erik_at_hensema.net>
Date: 2005-09-06 21:13:08 CEST


I've got a website for which I'm using svn to do version control.
Currently the following branches exist:


De docroot of the site is a working copy. Today I've upgraded the live
site from site_1_0 to site_1_1:

svn copy $repo/trunk $repo/branches/site_1_1 \
  -m 'Create a branche for site 1.1'
cd $docroot
svn switch $repo/branches/site_1_1

This had the desired effect: the trunk was now copied to site_1_1 and
the site was upgraded.

However, sometimes I need to do fixes to the live site, directly in
the docroot. This is where the problems start: most files have state
"S" in this 'svn status' output. svn completely ignores any change to
these files. They can't be reverted, they can't be commited.

So, what to do? I want to commit my changes to the site_1_1 branch and
I don't want downtime for the site if I can help it.

Erik Hensema (erik@hensema.net)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 6 21:15:14 2005

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.