Bruce Stephens <[EMAIL PROTECTED]> writes:
[...]
> So that leaves me with a different subversion repository, but a
> monotone database that's fine up to some revision (well, there are
> some minor differences caused by little bugs in the older Tailor,
> but that's just a one off commit to fix).
>
> So how can I join up the two? What I want to avoid is Tailor
> deciding to add all the files: they're all there!
OK, it was easier than I feared. So here's the hack, should anyone
else find themselves in a similar situation. It's a patch to
tailor.py, which is most definitely not suitable except for this kind
of exceptional situation:
94c94,95
< pendings = dwd.getPendingChangesets()
---
> revision = self.config.get(self.name,'start-revision', None)
> pendings = dwd.getPendingChangesets(revision)
140,143c141,144
< if not self.exists():
< self.bootstrap()
< if pconfig('start-revision') == 'HEAD':
< return
---
> ## if not self.exists():
> ## self.bootstrap()
> ## if pconfig('start-revision') == 'HEAD':
> ## return
Then I checked out the right revision from subversion, and constructed
a suitable MT directory (for monotone): basically you just do
"monotone setup", and put an appropriate revision into MT/revision.
Then made sure they were the same (using "monotone ls missing",
"monotone ls unknown", "monotone status --brief", and so on, and
making sure there's no Tailor .state file). Then put the revision
number in start-revision, and Tailor seemed to work from there.
Obviously this involved a fair amount of making and restoring tarball
backups and things before I got it right, but it did work.
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
