Lele Gaifax wrote: > there's no sign on /trunk that a new branch has born > somewhere else, and this means that tailor should fetch the log about > /branches as well (to stay in the svn example); that in turn means > that tailor would need to fetch both /trunk and /branches at the same > time...
Sure, it needs to see the whole repo, but it is pretty easy and light to do with: svn log -v /reporoot -r current_rev:HEAD or the equivalent underlying library call. But it wouldn't need to check out every copy of every branch ever made just to add one new changeset to a new branch. Instead it could just issue "svn cp" and "svn commit" as needed inside the (sparsely populated) working copy. (That's what I do by hand when I'm moving things around. I admit that there are some interesting bugs in svn when you "svn up -N" selectively, but it should be getting better...) > What's the problem with tracking the whole repo, eventually filtering > out unwanted dirs with a precommit? I was mostly worried about the bandwidth strain to the server and the resulting working copy sizes made by Tailor (I have never checked out all the branches and tags at once out of our local repositories, it would be huge). However, it turns out that despite the big revision numbers there are only less than 20000 revisions and only some dozens of branches. I guess that's feasible to get even if I wouldn't need it... And I might still use a precommit filter like you suggest to get a cleaner local version of the repo. I get still various errors, whether I set start-revision to INITIAL, 1 or the actual first revision. I guess this is because of repo reorganizations (renames), but I should be able to conquer that. E.g. Tailor issues svn co --quiet --ignore-externals --revision initrev http://repo/[EMAIL PROTECTED] srcpath 2>&1 In my case this should be http://repo/[EMAIL PROTECTED], since I only know the current path to the repo. Or I need to manually find out the original name first and use that: http://repo/[EMAIL PROTECTED] Thanks for your advise, it helps to know that mirroring full repo is the preferred way to go. Regards, Risto Kankkunen _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
