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

Re: Property Commit Problem

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-05-09 19:22:24 CEST

bryanalvord@vaticor.com (Bryan Alvord) writes:

> My working copy is up to date. Every time I have tried setting these
> properties, I have done it after committing all other changes.

Directories have version numbers too, remember. If your working copy
directory's revnum != HEAD, then your property commit will be

If you have a working copy fully at revision 5, and then commit a file
change, the working copy is *still* at revision 5 ... that is,
everything except the file you committed; it has a higher revision

So just because you were the last one to commit, *doesn't* mean your
working copy is "up to date". In terms of -content-, yes, it may be
exactly equal to the HEAD revision. But not in terms of revision
numbers. That's why you need to run 'svn up' before committing a
propchange. Even if you receive no changes, at least your entire wc
will all be at the same HEAD revision number.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 9 19:23:24 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.