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

Re: consecutive commit problem

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-04-28 15:38:17 CEST

Dan Allen <dan@mojavelinux.com> writes:

> My graphic designer is having a terrible time with the new version
> of SVN. Whenever he changes a file, commits it, changes it again
> and then tries to commit a second time, it complains that the file
> is out of date, even though he is the only one committing in that
> folder. It seems to be a very consistent issue. Is this a known
> bug?

Never heard of such a bug.

It sounds like one of two things is happening:

  1. the commit isn't actually happening on the server. running 'svn
      log' will verify that.

  2. perhaps his working copy isn't being properly processed after
      the commit succeeeds on the server. (e.g. maybe the
      version-resource-url cache isn't being changed.)

We need to see a reproduction recipe with details in order to help

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 28 15:40:06 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.