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

Re: single file commit forces no update when committing from different WC

From: Stephan Zeissler (KUTTIG) <stephan.zeissler_at_kuttig.com>
Date: 2006-07-17 10:34:03 CEST

Hi Lorenz,

Afaik, it like the following:
you only have to update your WC before commit, when you want to commit a
file or a folder that has been modified before.
If you have two files in your folder, and you modify both in seperate
WCs, and commit each one, thats ok,
but if you try to commit the folder itself, you'll get an Out-Of-Date error.

Greetings
 Stephan

Lorenz wrote:
> Hi all,
>
> I have two WCs based upon the same folder in the repository.
>
> I changed one file in the first WC and committedthe file only (not the
> whole WC).
>
> I then change some other files in the second WC and committed from the
> WC root.
>
> To my surprise I got no "out of date" warning, forcing me to update
> first.
>
> Until now I had the impression, that any commit from one WC would
> require to update a second WC of the same repo folder before
> commiting.
>
> Can someone please explain that behaviour?
>
>
> Lorenz
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 17 10:36:06 2006

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

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