[crossposting to dev@]
On Jun 28, 2005, at 11:11 AM, leo wrote:
> I want to use svn:externals to get the required modules into the main
> project. when svn:externals points to a tag of the module it works
> fine.
>
> but when svn:externals points to the trunk of the module, I have some
> problems.
> when working on the head of both the main project and the module
> all is ok.
> but when I
> want to update the project to a previous revision, I still get the
> head
> revision of the module. I expected to get the specified revision
> for both
> main project and the module.
>
> I know that I can specify the revision in the svn:externals
> property but
> this is not
> possible for already commited versions.
>
> Can someone explain this behaviour or give me hints in using
> svn:externals?
>
Hm, this might be a bug. What you're saying is that 'svn up -r X'
updates the working copy to revision X, but updates the externals to
HEAD?
Developers, should we file this?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 28 18:23:55 2005