Seems like you've got two thinks not entirely clear about SVN. :)
First: SVN has no concept of per file version numbers. A new revision
number is for the entire repository. Check in one modification and
you've got a new revision number for the state of the repository on the
moment your commit finisched. Combine this with the atomicity of SVN and
you're very happy with this.
Second: When you update a file in the trunk this has no effect on the
copy of the file in a branch and vice versa. For as far as SVN is
concerned those files that you like to think of as one entity are
actually two completly separeted entities in your repository. Only thing
in comon is that at some point a copy was made based in a previous
revision of a the file. Hope this clears things up a bit.
>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?
>
>When this works I'll do a branch of a branch and look what
>will happen :-))
>
>Thanks!
> Markus
>
>---------------------------------------------------------------------
>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 Oct 25 17:12:07 2004