--- "Finley, Stephen" <stephen.finley@fmr.com> wrote:
> Hi all
>
> I am not sure if I am missing something with
> externals or not.
>
> I set the properties on a directory to be an
> external to a specific
> revision. If I do an update at the top level I get
> the correct code, but
> if I do an update on the external directory I get
> the latest code for
> those files not the revision. I believe this is an
> error in subversions
> handling of externals.
>
> I hope what I am saying makes sense.
>
>
> Example.
>
> Myproject has property set to use external revision
> 5 of
> myproject2/common-files in directory common-files
>
> So you would end up with the directory
>
> /myproject/common-files
>
> If I do any update on the myproject directory it
> would get the correct
> version of the files, but if I went and did an
> update on the
> common-files directory it would update to the latest
> version of these
> files in /myprojects/common-files not version 5.
>
>
>
> Thank for any help
>
> Steve
When you do the svn up on the myproject directory (i.e
svn up .) the svn:external tag indicates to update to
version 5 of the common-files.
When you specifically perform an update on
common-files (i.e. svn up common-files) you are
telling it to update the contents of the common-files
to update to the HEAD revision.
I don't feel that this is in error. My understanding
is that common-files essentially is a separate working
copy from my-project. Which is why commands like "ci"
don't work seamlessly across both.
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 5 19:28:56 2007