"Matt Pounsett" <matt.pounsett@cira.ca> wrote in message
news:A133857A-01DC-11D9-9F52-000A95B212E6@cira.ca...
>
> On Sep 08, 2004, at 16:09, Edward Diener wrote:
>
> >>
> >> Now.. you're correct that there's a .svn directory at trunk/conf/.svn/
> >> which says that trunk/conf/foo and trunk/conf/bar belong to RepoB.
> >> But
> >> there's also a .svn directory at trunk/.svn/ which says that all of
> >> trunk/conf belongs to RepoA.
> >
> > I hope you are kidding that an .svn file contains information about
> > all .svn
> > directories below it as to what those individual directories point to.
> > What
> > a horrendous design decision that would be.
> >
>
> I didn't say .svn directories contain information about all directories
> below the current directory. I said it contains information on all the
> directories IN the current directory.
I do not understand the difference.
>
> So trunk/.svn contains information about trunk/conf. The implication
> of this though is that all of trunk/conf is part of the same repository
> as trunk.
OK, I see what is being done. Each directory has the information for each
file in it and a subdirectory is just another file within a particular
parent directory.
My suggestion then is to fix svn switch so that it allows another repository
path entirely and is not limited to the same repository as its parent
directory if its parent directory is under svn control. I would much rather
use this than any kludge. Unfortunately my design right now necessitates
allowing a subdirectory to access files in a different repository than itsd
parent directory. I guess I will have to change this <g> .
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 8 23:49:52 2004