[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: let's kill svn:externals

From: SteveKing <steveking_at_gmx.ch>
Date: 2003-07-23 20:14:36 CEST

----- Original Message -----
From: "Garrett Rooney" <rooneg@electricjellyfish.net>
> > Now: with every "svn up" the externals also get updated. When doing that
> > check the HEAD revision of the external project and store that inside
> > another property (e.g. svn:externalsrev) which is invisible to the user.
> > If you do a "svn copy" now all you have to do is replace the "HEAD"
> > of the original svn:externals property with that stored revision number:
> > "folder HEAD http://myurl" -> "folder -r 888 http://myurl"
> The problem with that is that when you have an external pointing to
> http://foo/repos/trunk/whatever, and you tag everything under trunk, it
> still points to trunk, where you would want it to point to the tag.
> This is the kind of thing that would make this sort of support useful,
> and the kind of thing that is difficult to implement at the moment.

You mean something like this?

Main Project located at
an svn:externals under http://foo/repos/trunk/folder
pointing to

now do an svn copy from the working copy of the main project
to http://foo/repos/tags/newtag

And now you want that the svn:externals points to


I don't think it should work that way. Just leave the externals on the
trunk - that's what the main project used when the tagging occured.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 23 20:15:38 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.