Thank you for your answer.
I also looked at the 'svn:externals' property as indicated by Ben.
But unfortunately, right now my conclusion is that I need both
svn:external, and the ability to commit my all project without having to
do it in each external directory/file, as I can do in a switched branch.
Any idea of when this could be possible ?
I understood that svn:external should be extended to allow this. Am I
Also, for the bug, the concept of copying a directory with a switched
subdirectory is still not clear. Should it copy the files of the
original subdirectory (before the switch) .. as it is the case when you
do the copy on the server (as you can't switch a server side directory,
or should it copy the files from the switched directory, as when you
perform the copy on your working copy ?
My guess would be that if you make a copy of a switched directory in
working copy, indeed, the file of the switched tree should be copied
(i.e. the bug). If this is the case, then maybe working with switched
directories, and having clean branches / tags can work for us until the
svn:external directories can be committed automatically with the all
Thanks again for your help,
On Tue, 2004-03-23 at 13:09, Philip Martin wrote:
> Sylvain Vieujot <firstname.lastname@example.org> writes:
> > # This is Ok, the file is updated in the library
> > $ svn copy project1/trunk/ project1/branches/v1WithSwitch
> > A project1/branches/v1WithSwitch
> > $ svn ci -m "branch project1"
> > Adding project1/branches/v1WithSwitch
> You have uncovered a bug, I have raised issue 1802. I suspect that
> copies like that are usually made using the URL-to-URL, or wc-to-URL,
> forms of the copy command and these appear to work better.
Received on Wed Mar 24 03:24:22 2004