<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">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>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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The more I think about it, the less convinced I am is that this space optimization is worth introducing such a fragile </blockquote><div><br></div><div>You uncovered one issue and you're calling it "fragile?" Proxy is a well-documented, proven pattern that has stood the test of time.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">machinery. MC is designed to have all ancestry info available at all times - just opening any repository will cause the proxies to materialize again, because the highlighting looks at which version names are in the ancestry of the working copy.<br>
<br>
I'd rather revert this whole thing, to be honest. If you're trying to build a minimal image for deploying an application you would be better off unloading MC altogether.<br></blockquote><div><br></div><div><br></div>
<div>It's not just about smaller images. It's about sustainability of the ancestry.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Bert -<br>
<br>
On 2013-08-15, at 18:26, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
<br>
> Ok, I'll look at it today. One thing is that all ancestry SHOULD be<br>
> in the same repository -- but I agree, the system needs to handle that<br>
> as gracefully as possible if it isn't.<br>
><br>
> Can you tell me how to reproduce the issue?<br>
><br>
> Thanks.<br>
<div class="im">><br>
><br>
> On Thu, Aug 15, 2013 at 10:39 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br>
>> It's not quite bullet-proof yet: log of DNU attached. It fails to find a certain info, which causes all kinds of problems.<br>
>><br>
>> Also, something apparently tries to materialize infos in the background. Possibly updating MC browsers, not sure. This leads to very strange and hard to get-rid-of notifiers:<br>
>><br>
>><br>
>><br>
>><br>
</div>>> (these updating bars used to be very rare, like once per session, recently they pop up multiple times for many operations, but I've never before had 2 on the screen at the same time)<br>
>><br>
>> - Bert -<br>
>><br>
>><br>
>><br>
>><br>
><br>
<br>
</blockquote></div><br></div></div>