On Fri, 26 Oct 2007 20:23:14 +0300 Risto Kankkunen <[EMAIL PROTECTED]> wrote:
> I'm trying to set up Tailor to mirror an SVN repository (to a local > SVN repository). > > I can pretty easily do that for a particular subdirectory, > like /trunk. But I'm at loss how to mirror change-sets > in /trunk /branches and /tags occurring after a specified revision. > > ... > > Basically I'd like to track /trunk and any tags and branches that are > created out of it. But I could settle for specifying what branches to > mirror in addition to /trunk and /tags. > > However, I don't see any way to specify multiple paths as a module. > And if I specify multiple projects, they are processed one after > another and cannot therefore maintain change-sets touching several > projects nor the order of the change-sets. > > Am I completely off-base here or is there really no way to support > this -- what I believe to be a common -- use-case? No, I'm afraid you can't do that: tailor has no notion of "branches" and a weak and mostly CVS-headed of "tags". Tailor needs to "see" the whole hierarchy it is migrating: for example under most VCs (and svn for sure) 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... What's the problem with tracking the whole repo, eventually filtering out unwanted dirs with a precommit? ciao, lele. _______________________________________________ Tailor mailing list Tailor@lists.zooko.com http://lists.zooko.com/mailman/listinfo/tailor