#120: Switch to "mtn automate"
----------------------+-----------------------------------------------------
Reporter: dhbaird | Owner: lele
Type: defect | Status: new
Priority: major | Milestone: VersionOne
Component: mtn | Version: 0.9
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Comment (by rghetta):
Sure using automate will make a more stable interface with monotone.
[[BR]]
There is already a python interface to automate, used by the "dumb"
monotone server. See monotone.py in branch net.venge.monotone.dumb[[BR]]
Perhaps the most difficult part is replicating the history linearization
trickery used by current backend. It relies heavily on having monotone
computing a reasonable changeset between two arbitrary revisions. AFAIK,
there is no automate command which replicates the standard "mtn diff",
giving out not only the differences between files, but also the metadata
(automate content_diff doesn't output metadata).
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/120#comment:6>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[EMAIL PROTECTED]
http://lists.zooko.com/mailman/listinfo/tailor
