[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 3597]  relocate should update relative externals
From:       cmpilato () tigris ! org
Date:       2010-10-28 20:32:28
Message-ID: 20101028203228.B35A4540146 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=3597



User cmpilato changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |STARTED
--------------------------------------------------------------------------------
        Target milestone|1.7-consider              |1.7.0
--------------------------------------------------------------------------------




------- Additional comments from cmpilato@tigris.org Thu Oct 28 13:32:27 -0700 2010 -------
I've been coding on this for the past couple of hours, and I came to a
realization:  whether an external uses a relative URL or not isn't the most
interesting factor here.  So I'm coding against this one instead:  whether the
external working copy's repository root URL matches that of the primary working
copy.  This way, relocation happens both on externals with relative URLs (which
will almost[1] always come from the same repository) and explicit URLs from the
same repository.

Commit coming soon.

-- C-Mike

[1] Subversion allows relative URLs which point to different repositories.  You
can use "../../../" and so on to "crawl up" out of your current repository URL
space and then down into another repository.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2676838

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]