[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: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-07-17 10:39:54 CEST

On 7/17/06, Lorenz <lorenznl@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':
; summary is: you can't commit to directories which aren't HEAD. This
applies to properties, adds, deletes and thus to copies and moves.



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:41:38 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.