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

Re: Update Required Threshold

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-02-22 21:23:49 CET

Young, Jason (GE Infrastructure) wrote:
> I think there more to it than that. I believe I have seen it in code
> that only I would have modified. Also, we had someone here get a lock
> on a folder, and when they went to commit, it said he needed to update.
> The log didn't show any changes on that folder.
> However, I haven't been able to reproduce this behavior locally.
> Something else is going on.

All that is covered in the Subversion book.

If you commit changes, Subversion checks the last-committed-revision, it
doesn't compare the whole commit with the repository. If the
last-committed-revisions don't match, you're asked to update first.

With files, that's usually not a problem. It works there as you might

But e.g. with properties you can get confused. Say you change the
svn:ignore property of a folder. Someone else has changed or set
svn:externals property on the same folder. Now even if you don't have a
conflict with those properties, the last-commit-revision of the folder
doesn't match anymore, because both properties (even though they're
independent) affect the same folder and changed its last-commit-revision.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Feb 22 21:24:05 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.