Thanks for simple option 1, it could solve our problem.
Option 2 doesn't fit, cause of needing to do bunch of "svn copy ..." to tag
all projects and then tag to BigProject with pinned externals.
Of course it could be done without tagging all projects, just pinning
externals to revision of trunk, bu
> 1. Yes you're right, but even though I've done committing and updating
> externals I got the same message "svn: 'BigProject-trunks\Project1' is not
> under version control".
>
> 2. The usual way to create a tag doesn't fit our need of tagging all
> projects within one revision.
>
> For better u
Hello,
1. Yes you're right, but even though I've done committing and updating
externals I got the same message "svn: 'BigProject-trunks\Project1' is not
under version control".
2. The usual way to create a tag doesn't fit our need of tagging all
projects within one revision.
For better understan
On May 28, 2010, at 10:18, Sergii Ostroverkhov wrote:
> CMD script for init test repository:
> svnadmin create BigProject
>
> echo [general] > BigProject\conf\svnserve.conf
> echo anon-access = write >> BigProject\conf\svnserve.conf
>
> svn mkdir -m Project1 svn://localhost/BigProject/Project1
>
Hello,
CMD script for init test repository:
svnadmin create BigProject
echo [general] > BigProject\conf\svnserve.conf
echo anon-access = write >> BigProject\conf\svnserve.conf
svn mkdir -m Project1 svn://localhost/BigProject/Project1
svn mkdir -m Project1 svn://localhost/BigProject/Project1/tag
