"Boelter Markus" <Markus.Boelter@Micronas.com> writes:
> That's why I'm asking. :-) I read this chapter several times,
> but was just not sure if it matches to my case. Now I got a
> "new" problem:
>
> Before a few mintues I modified a file in the trunk which is
> in all branches. After the commit I did a svn up in one of
> the branches. The only feedback I got was "At Revision 48" -
> noting else. A look in the files showed no modification. svn
> up again did nothing.
>
> It seems like the branch recognized a change, made a new
> Revision (from 46 to 48), but no changes to the file were made. Why?
This is expected behavior. When you branch a tree, you make a copy of
it. After that, changes to the original tree do not affect the copy.
Subversion does not implement so-called "shadow branches" or "alias
branches", whereby some of the files track their originals, and others
stay on the branch (or track both changes in the original *and*
changes in the branch... this can get quite complex!).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 17:16:43 2004