On Thu 30 Mar 2006 07:42, subversion@sensor-technik.de wrote:
> I think I wasn't exact enough at the example. The problem is when I commit
> a folder in which I changed a file and a newer revision of that folder is
> in the repository because someone else committed another file to that
> directory, I doesn't get an out-of-date error.
>
> Let's take the example I used before. The repository layout is:
>
> repo/
>
> |--foo/ (10)
> |
> | |-bar1.c (10)
> | |-bar2.c (10)
> | |-...
>
> - Harry has a working copy of foo on his local disk in directory foo1
> - Harry changes bar1.c in directory foo1
> - He commits foo1 to foo in the repository -> foo and bar1.c are now in
> rev. 11
>
> - Sally has a working copy of foo on her local disk in directory foo2
> - Sally changes bar2.c in directory foo2
>
> So far so good. But if now Sally commits her changes to foo, subversion
> doesn't come up with an out-of-date error. Of course, bar2.c is not out of
> date, but foo2 is and I think that Sally should be notified about the
> changes in bar1.c.
>
> After Sally has committed her changes, foo is in rev. 12 and neither Harry
> nor Sally has a working copy that matches the repository.
>
> I wonder if this is intended...
>
Yes, this is the intended behaviour.
> Regards
> Christoph
>
[snipped]
--
John Allen mailto:john.allen@moyville.net
Mandriva Club Member(Silver) http://www.moyville.net
Mandriva Linux release 2006.0 (Official) for i586, kernel 2.6.12-15mdk
08:46:01 up 6 days, 21:58, 1 user, load average: 0.05, 0.32, 0.35
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 30 09:46:46 2006