[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: Jody Shumaker <jody.shumaker_at_gmail.com>
Date: 2006-02-23 15:40:37 CET

> 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?

It will let you. The only complex situation i've seen is when
changing properties on a directory. Since a directories latest
Revision number increases anytime any of its contents are changed,
you will have to have the directory updated if any of its contents
have changed before you can commit a property change to it. This makes
sense though, because the change to contents of the folder may be
impacted by the property change you're about to do.

Of course there's one case where this happens even if the contents of
the directory are not different server side. When you commit changes
to files in a directory, you end up with a mixed revision directory
where a file may be revision 101, but the directory is still revision
100. Even if nothing has changed server side, you'll have to do an
update before you can commit a change on the directory. Mainly because
when you did the earlier commits, it can't safely say the directory
matches the latest revision without an update.

- Jody

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:40:56 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.