We already break backwards compatibility for reading ~/.svk/config when going from 1.0x to trunk due to the upgrade from YAML < 0.60 to YAML-Syck in trunk. So changing DH to an incompatible format in trunk doesn't really change anything as far as backwards compatibility with
1.0x is concerned. It's gone anyway. Of course it would be nice if 1.0x would know how to use DH-0.40 as well so that you coud still use 1.0x and trunk at the same time if you upgraded both YAML to 0.60 or later and DH to
0.40 or later for 1.0x.<br><br>Michael<br><br><br><div><span class="gmail_quote">On 11/4/06, <b class="gmail_sendername">Chia-Liang Kao</b> <<a href="mailto:clkao@clkao.org">clkao@clkao.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 04/11/06, David Glasser <<a href="mailto:glasser@mit.edu">glasser@mit.edu</a>> wrote:<br>> However, if you do choose to upgrade to DH 0.40, older versions of SVK<br>> may break; at the very least, some of the checkout subcommands like
<br>> "svk co -l" and "svk co --relocate" did not work on trunk with DH 0.40<br>> until r2110; I have no idea how SVK 1.0x behaves with DH 0.40.<br><br>We should make sure newer d::h doesn't break old svk. Possibly by
<br>releasing new D::H under different name.<br><br>Cheers,<br>CLK<br>_______________________________________________<br>svk-devel mailing list<br><a href="mailto:svk-devel@bestpractical.com">svk-devel@bestpractical.com</a>
<br><a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel</a><br></blockquote></div><br>