Yeah in svk sparse working copies actually work well already :)<br><br>Michael<br><br><br><div><span class="gmail_quote">On 10/18/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 18/10/06, Derek Atkins <<a href="mailto:warlord@mit.edu">warlord@mit.edu
</a>> wrote:<br>> Aha!! Excellent. And I presume that SVK is smart enough not<br>> to consider these "local changes" as "deletes" so that when I<br>> 'svk commit' and eventually push back to the Subversion repository
<br>> "the right thing" will happen? Excellent! Thanks!<br><br>Not unless you specify --import when doing svk commit. So you can<br>actually do it if you want, like importing the current snapshot as the<br>
new revision.<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>