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

Should a working copy always be up-to-date after a successful commit?

From: Roel Harbers <roel_at_roelharbers.nl>
Date: 2004-05-07 13:05:28 CEST

I tried to do the following:

D:\svn>svn co file:///D:/svn/Repositories/Test
A Test\dir1
A Test\dir1\dir2
Checked out revision 28.

D:\svn>cd Test

D:\svn\Test>svn status -u
Status against revision: 28

D:\svn\Test>svn delete dir1\dir2
D dir1\dir2

D:\svn\Test>svn commit -mtest
Deleting dir1\dir2

Committed revision 29.

D:\svn\Test>svn delete dir1
D dir1

D:\svn\Test>svn status -u
D 28 dir1
Status against revision: 29

D:\svn\Test>svn commit -mtest
Deleting dir1
svn: Commit failed (details follow):
svn: Out of date: 'dir1' in transaction '30'

Now, I understand that this can be easily fixed with a "svn update"
before the last commit. But isn't it strange that after I commit, the
working copy contains an out-of-date directory? Shouldn't a successful
commit guarantee that the commited wc is up-to-date?

I think the problem is that dir2 isn't actually deleted from the wc's
file system until after the commit. Then, the fs-delete of dir2 changes
the properties of the dir1 directory, and svn thinks dir1 has changed.

Of course, I could be completely misunderstanding what happens here.


Roel Harbers

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 7 13:06:06 2004

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.