RE: Re: Update Required Threshold

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.

Jason

-----Original Message-----
From: Johan Appelgren [mailto:johan.appelgren@gmail.com]
Sent: Wednesday, February 22, 2006 1:35 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Update Required Threshold

On 2/22/06, Young, Jason (GE Infrastructure) <Jason.Young@ge.com> wrote:
> Is there a certain number of revisions that a working copy needs to be

> behind by before an update is required?
>
> We sometimes get prompted to do an update before we can commit. Other

> times, we do not. What is the logic for deciding when that should
> happen? I would think that it would check the revision number against

> that path in the repository and prompt if they are different.
> However, it doesn't seem to work that way.

Usually it is because you are trying to commit a file that someone else
has commited to since you last updated your working copy. Not sure if
there are other circumstances that causes the prompt to update the
working copy.

/Johan

---------------------------------------------------------------------
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 Wed Feb 22 21:06:10 2006