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

Re: Can't commit after switching working copy

From: Stephan Zeissler <stephan.zeissler_at_kuttig.com>
Date: 2005-09-07 10:23:04 CEST

Erik Hensema wrote:

>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.

Hi Erik,

what kind of editor do you use to edit the files in the site?
AFAIK SubVersion uses the timestamp at first level to identify if a file
has changed. If your editor do not modify the timestamp, subversion does
not know that it has been modified.
try to touch the file, maybe it then works.

 Stephan Zeissler

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 7 10:24:48 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.