<div dir="ltr">On Thu, Aug 15, 2013 at 9:48 AM, Chris Muller <span dir="ltr"><<a href="mailto:ma.chris.m@gmail.com" target="_blank">ma.chris.m@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div class="im">On Thu, Aug 15, 2013 at 11:39 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It happens to not find "XML-Parser-Alexandre_Bergel.20". No idea why it's trying to look for that. Not all merged versions are in trunk, by design.<br>
</blockquote><div><br></div></div><div>The original MC documentation says ALL versions are intended to be contained by repositories. I have no idea what "design" you're talking about.</div></div></div></div>
</blockquote><div><br></div><div>so, all versions are in a repository somewhere. Maybe in SqueakSource (now read only?), SmalltalkHub, GitHub, SS3, or even on my local file directory repository. Not all of those are shared - or constantly attached to the image you are working with. The machinery needs to work with missing versions - which Monticello does - it just goes farther back until it can find a common ancestor. </div>
<div><br></div><div>I'm probably missing something, but couldn't the proxy resolve itself with the data contained in the .mcz should it need to? The data is there in the first place, and should be easier to get at than web calls to repositories (or directory scans, for that matter).</div>
<div><br></div><div>-Chris</div></div></div></div>