You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Lorenz <lo...@yahoo.com> on 2006/07/17 07:03:03 UTC

single file commit forces no update when committing from different WC

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

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

Posted by Erik Huelsmann <eh...@gmail.com>.
On 7/17/06, Lorenz <lo...@yahoo.com> 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?

Generally, you can commit your changes to any file which hasn't been
changed in the repository, even if the repository had commits to other
files. This applies to 'content changes'.

There actually is a section on this in 'The Book', which also
explicitly addresses 'tree changes':
http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs.limits
; summary is: you can't commit to directories which aren't HEAD. This
applies to properties, adds, deletes and thus to copies and moves.

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

Posted by "Stephan Zeissler (KUTTIG)" <st...@kuttig.com>.
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