subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Les Mikesell <lesmikes...@gmail.com>
Subject Re: Feature request: allow for relative working copy paths in svn:externals definition
Date Fri, 02 Mar 2012 16:19:08 GMT
On Fri, Mar 2, 2012 at 9:58 AM, Humm, Markus
<Markus.Humm@de.ebmpapst.com> wrote:
>
>>> We created a Junction inside D:\Test\Projekt1 named
>>> D:\Test\Projekt1\JunctionTest which points to D:\Test\Common
>>
>> Can you do this the other way around?  That is, make D:\Test\Common
> the junction point, pointing to wherever your svn external is going to
>> drop the files?    And figure out what it is you really want to happen
>> in the case where you want to check out D:\Test\Projek1 and
>> D:\Test\Projek2 and they both have the same relationship to
> D:\Test\Common but want different revisions to appear there.
>
> No, the other way round doesn't work, because d:\Test\Common cannot
> point at the same time both to
> D:\Test\Projekt1\JunctionTest and D:\Test\Project2\JunctionTest. We just
> tested this. The question now is, why does SVN detect our hardlinked
> directory as special type of directory and thus creates us pain? (as
> otherwise we'd have a solution which could work for us)

I think you are going to have a very, very confusing time if you do
get the common directory to simultaneously be junctioned (either
direction) to externals that can be pointed at different revisions.
What is it you would like to happen in that case?

-- 
   Les Mikesell
     lesmikesell@gmail.com

Mime
View raw message