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

RE: Re: Update Required Threshold

From: Young, Jason \(GE Infrastructure\) <Jason.Young_at_ge.com>
Date: 2006-02-23 15:10:31 CET

Thanks for your time, I know you are very busy.

All I could find in the subversion book was this:
"The repository doesn't know or care if your changes make any sense as a whole; it only checks to make sure that nobody else has changed any of the same files that you did when you weren't looking. If somebody has done that, the entire commit will fail with a message informing you that one or more of your files is out-of-date"

So are you saying that it will only fail if you attempt to commit a file that was had it's revision number updated on the server? And does that also mean that if I check out 10 files, and 9 changed on the server, and I changed the 10th, that it will let me commit it?

Should I ask this on the Subversion mailing list? I thought maybe the behavior was part of Tortoise, but I may have been wrong.

Thanks for your help,

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Wednesday, February 22, 2006 2:24 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Update Required Threshold

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 expect.

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
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Feb 23 15:12:49 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.