[EMAIL PROTECTED] ha scritto:
I am still using the cvsync version
of tailor, because I have some very large projects, and I haven't had
the time to try to upgrade.
I used to do this kind of bidirectional sync with a single tailor instance in
old tailor, too.
But in the new version of tailor, one directory is marked as "source" and the
other is marked as "target". I haven't tried hacking the tailor config in
between invocations to change those marks and see if new tailor can do this
same trick that you are doing with old tailor.
How I imagined it was something like
[DEFAULT]
working-policy=a-patch-at-a-time-looping-over-projects-till-there's-work
[svn2darcs]
source=svn:repo
target=darcs:repo
root-directory=somedir
[darcs2svn]
source=darcs:repo
target=svn:repo
root-directory=somedir
[darcs:repo]
repository=server:master/repo
[svn:repo]
repository=svn://server/master/trunk
module=something
Is this expressing the idea? The "working-policy" concept is totally
vaporware at this time...
bye, lele.
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
