Eek. *don't* file in the last two methods in <span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">SourceFileReadOnlyCopy.1.cs as they screw up version scanning during condensation.</span><div>
<span class="Apple-style-span" style="font-size: 13px; "><span id=":1l9"></span></span><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><br>
</span></font><br><div class="gmail_quote">On Wed, May 19, 2010 at 12:05 PM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi All,<div><br></div><div> I'm a bit late to this party but I just had cause to condense changes in an image but wanted to retain most version history. By most I mean I want to retain the linear history (a method's direct ancestor versions), not the full history including reversions. So if one has a set of stamps like</div>
<div><div><span style="white-space:pre"> </span>eem 7/7/2009 20:06<span style="white-space:pre"> </span>7 July 2009 8:06 pm</div><div><span style="white-space:pre"> </span>eem 6/18/2009 19:21<span style="white-space:pre"> </span>18 June 2009 7:21 pm</div>
<div><span style="white-space:pre"> </span>eem 5/5/2009 12:16<span style="white-space:pre"> </span>5 May 2009 12:16 pm</div><div><span style="white-space:pre"> </span>eem 6/18/2009 19:19<span style="white-space:pre"> </span>18 June 2009 7:19 pm</div>
<div><span style="white-space:pre"> </span>eem 6/18/2009 18:57<span style="white-space:pre"> </span>18 June 2009 6:57 pm</div><div><span style="white-space:pre"> </span>eem 5/5/2009 12:16<span style="white-space:pre"> </span>5 May 2009 12:16 pm</div>
<div><span style="white-space:pre"> </span>eem 6/18/2009 18:17<span style="white-space:pre"> </span>18 June 2009 6:17 pm</div><div><span style="white-space:pre"> </span>eem 6/18/2009 18:14<span style="white-space:pre"> </span>18 June 2009 6:14 pm</div>
<div><span style="white-space:pre"> </span>eem 6/18/2009 18:06<span style="white-space:pre"> </span>18 June 2009 6:06 pm</div><div><span style="white-space:pre"> </span>eem 5/5/2009 12:16<span style="white-space:pre"> </span>5 May 2009 12:16 pm</div>
<div><span style="white-space:pre"> </span>eem 5/4/2009 19:19<span style="white-space:pre"> </span>4 May 2009 7:19 pm</div><div>the direct ancestry is</div><div><span style="white-space:pre"> </span>eem 7/7/2009 20:06<span style="white-space:pre"> </span>7 July 2009 8:06 pm</div>
<div><span style="white-space:pre"> </span>eem 6/18/2009 19:21<span style="white-space:pre"> </span>18 June 2009 7:21 pm</div><div><span style="white-space:pre"> </span>eem 5/5/2009 12:16<span style="white-space:pre"> </span>5 May 2009 12:16 pm</div>
<div><span style="white-space:pre"> </span>eem 5/4/2009 19:19<span style="white-space:pre"> </span>4 May 2009 7:19 pm</div><div><br></div><div>This probably isn't useful as the default condense changes mechanism but its probably useful to a few of you, so here it is. The first change set provides shared read-only copies of the sources files for faster version scanning. The second change set provides the code to extract the direct ancestry and a hack in ClassDescription>>fileOutChangedMessages:on:moveSource:toFile: to force use of ClassDescription>>printMethodChunkHistorically:on:moveSource:toFile: when condensing. If y'all think this is generally useful we can make "condense preserving history" an option alongside condenseChanges, condenseSources et al.</div>
<div><br></div><div>HTH</div><div>Eliot</div><div><div></div><div class="h5"><div><br><div class="gmail_quote">On Wed, Mar 31, 2010 at 11:34 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de" target="_blank">andreas.raab@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi -<br>
<br>
I just posted the code condensing sources in 4.1. It looks like it works fine; if anyone wants to try it (in a throwaway image please!) run it via:<br>
<br>
Smalltalk appendChangesTo: 'mytest.sources'.<br>
<br>
This will copy the old sources, append the condensed changes and run the image with the new sources file. Everything should continue to work as is, but method histories should show both, the latest 4.1 version and the original 4.0 version (but not the intermediates).<br>
<br>
Cheers,<br><font color="#888888">
- Andreas</font><div><div></div><div><br>
<br>
<br>
On 3/29/2010 1:59 PM, Andreas Raab wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi -<br>
<br>
I just wanted to float an idea that Eliot came up with over lunch. He<br>
pointed out that it would be good if we could preserve the method<br>
history from 4.0 but that it also would be good if we could ship with an<br>
empty changes file. Both of which can be achieved if we'd be condensing<br>
the changes file *to the end of* the sources file, i.e,<br>
<br>
SqueakV41.source = SqueakV4.sources + Squeak4.1.changes<br>
<br>
This has some advantages besides the empty changes file. It allows us to<br>
keep up with the intermediate stages during the RCs. In other words, for<br>
the next RC I can make a SqueakV41.sources and the image will be<br>
"compatible" with later versions of the sources file. In fact,<br>
SqueakV41.sources would be compatible with with SqueakV40.sources, too,<br>
so you could link the old sources file to the new one to save space if<br>
desired.<br>
<br>
What do people think? Sounds like a plan?<br>
<br>
Cheers,<br>
- Andreas<br>
<br>
<br>
</blockquote>
<br>
<br>
</div></div></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>