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

Re: Weird need for "svn update"

From: Tyler Roscoe <tyler_at_cryptio.net>
Date: Wed, 10 Jun 2009 08:11:17 -0700

On Wed, Jun 10, 2009 at 03:27:54PM +0200, Neels Janosch Hofmeyr wrote:
> mkdir dir
> echo fool > dir/foo
> svn add dir
> svn ci -m log1

As soon as you commit here, you have changed the repository:
revisionNumber++.

> ## The problem disappears when removing this edit:
> echo once > dir/foo
> svn ci -m log2

So when you go to commit here, you're using a working copy that doesn't
have the "latest" from the repo, hence the error. Yes, that change came
from this very working copy, but I'm guessing there are weird corner
cases you can get into if your working copy doesn't force you to update
here before committing something else.

hth,
tyler
Received on 2009-06-10 17:12:15 CEST

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