<br><br><div class="gmail_quote">On Tue, Mar 9, 2010 at 7:09 PM, Colin Putney <span dir="ltr"><<a href="mailto:cputney@wiresong.ca">cputney@wiresong.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 2010-03-10, at 1:17 AM, <a href="mailto:commits@source.squeak.org">commits@source.squeak.org</a> wrote:<br>
<br>
> Put the newer version check back into saveVersion. It prevents accidental commits when there are newer (unmerged) versions in the repository. The test got lost probably accidentally a while ago; if the removal was deliberate we should make this a preference (I'm too lazy to live without it :-)<br>
<br>
</div>I removed it because it's completely unnecessary. Monticello has no problem committing when there are newer versions out there. In fact, in that situation is better to commit anyway, and merge afterwards.<br></blockquote>
<div><br></div><div>But I find knowing there's a newer version is /really/ useful. It's all too easy to miss that someone else has updated your pet package with good stuff and plough on loosing their changes in the mists of time. I vote for keeping the check-in. It doesn't stop you form committing but has the huge advantage of knowing that a merge might be in your future.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
Colin<br>
</font></blockquote></div><br>